I think part of the problem is that the RFC was written against a byte-stream, but we're running the parser against a character stream.
On Thu, Oct 15, 2009 at 9:18 AM, Xuefeng Wu <[email protected]> wrote: > Thank you for your information. > What we should do for this now? > let the wrong thing stay or find out a resolution? > > > On Thu, Oct 15, 2009 at 6:40 PM, Vassil Dichev <[email protected]> wrote: > > > > Why the name is *escape*, anyone could explain? > > > > I think most of the MsgParser concerning URLs is transformed from > > RFC1738 (http://www.faqs.org/rfcs/rfc1738.html) BNF notation into > > Scala using parser combinators. So for any inconsistencies you've > > found the point of reference is this RFC. > > > > As for the escape, it's a special character which modifies the meaning > > of the following characters (more info here: > > http://en.wikipedia.org/wiki/Escape_character). In the RFC the escape > > is defined like this: > > > > escape = "%" hex hex > > > > > > -- > Global R&D Center,Shanghai China,Carestream Health, Inc. > Tel:(86-21)3852 6101 > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics
