My guess is that there's some route issue inside kernel. Linux or USAGI guru out there, any hints?
My guess is that there's some route issue inside kernel. Linux or USAGI guru out there, any hints?
...The most successful key telephone system in the world has a design limitation... when you determine the number of times your phone will ring before it forwards to voicemail, you can choose from 2, 3, 4, 6, or 10 ring cycles. Have you any idea how many times people ask for five rings? Yet the manufacturers absolutely cannot get their heads around the idea that this is a problem. That's the way it works, they say, and users need to get over it.And another story:
...the name you program on your set can only be seven characters in length. Back in the late 1980s, when this particular system was built, RAM was pretty dear, and storing those seven characters for dozens of sets represented a huge hardware expense. So what's the excuse today? None. Are there any plans to change it? Hardlyâthe issue is not even officially acknowledged as a problem.Funny. Comparing to that situation, customers today are a little spoiled ^_^
A physicist, an engineer, and a computer scientist were discussing the nature of God. "Surely a physicist," said the physicist, "because early in the Creation, God made light; and you know, Maxwell's equations, the dual nature of electromagnetic waves, the relativistic consequences..." "An Engineer!," said the engineer, "because before making Light, God split the Chaos into Land and Water; it takes a hell of an engineer to handle that big amount of mud, and orderly separation of solids from liquids..." The computer scientist shouted:" And the Chaos, where do you think it was coming from, hmm?"
_________________
ps. discovered Sun Net Talk Program. It's a must to visit.
In general, a character is reserved if the semantics of the URI changes if the character is replaced with its escaped US-ASCII encoding. -- section 2.2or
Implementers should be careful not to escape or unescape the same string more than once, since unescaping an already unescaped string might lead to misinterpreting a percent data character as another escaped character, or vice versa in the case of escaping an already escaped string. -- section 2.4.2These can be real bugs in specific implementation! RFC is RFC. If one get to read it, read it very carefully :-)