Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of feeder.of.the.bears@gmail.com
 designates 209.85.211.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=OwpKNFsfZxdEa1IXh+U3+btXHPZ0dgkrrEYAbwy8aZC78J3L1HqcZcTpsrIuUgueu4
         WufINIy/6Zw+LQmZQASv+cQ7V086er1YpjcSH3oqVpaLTvyd9DJgOK9NJjhgqSqs5Sy7
         xir6sXKvMBTvJedliOwigoux6+IxIJagvbTx4=
MIME-Version: 1.0
In-Reply-To: <4db64d890910150918l2701e07difc21c223285fdeb7@mail.gmail.com>
References: <4db64d890910140128m51edcae5o8e8871cc29523ce5@mail.gmail.com>
	 <4db64d890910140218y21668d48kc532920fdf875465@mail.gmail.com>
	 <4db64d890910140221g71836e42ud420026ac4a42077@mail.gmail.com>
	 <4db64d890910142141q2fa88340j8f7fc2da56b5275e@mail.gmail.com>
	 <fa2d9f450910142249v56fc5d00n9f84042b2669b863@mail.gmail.com>
	 <4db64d890910150056s3ac6ef35g448d6fe797c50137@mail.gmail.com>
	 <4db64d890910150251h74079ab6jf0a733c3190ebc40@mail.gmail.com>
	 <4db64d890910150259o1ba9ba54lf516950c998626a8@mail.gmail.com>
	 <c7fc82820910150340u6ea3c87cq6bb6682738fe99@mail.gmail.com>
	 <4db64d890910150918l2701e07difc21c223285fdeb7@mail.gmail.com>
Date: Thu, 15 Oct 2009 10:00:10 -0700
Message-ID: <cdbebedf0910151000w240d423s6fdc0411197f63d@mail.gmail.com>
Subject: Re: ESME-26 The message parser should ignore # in urls
From: David Pollak <feeder.of.the.bears@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=00163630ef47562eac0475fc36bf

--00163630ef47562eac0475fc36bf
Content-Type: text/plain; charset=UTF-8

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 <benewu@gmail.com> 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 <vdichev@apache.org> 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

--00163630ef47562eac0475fc36bf--