Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 78279 invoked from network); 15 Oct 2009 17:14:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Oct 2009 17:14:45 -0000 Received: (qmail 30570 invoked by uid 500); 15 Oct 2009 17:14:45 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 30528 invoked by uid 500); 15 Oct 2009 17:14:45 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 30518 invoked by uid 99); 15 Oct 2009 17:14:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2009 17:14:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of feeder.of.the.bears@gmail.com designates 209.85.217.222 as permitted sender) Received: from [209.85.217.222] (HELO mail-gx0-f222.google.com) (209.85.217.222) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2009 17:14:33 +0000 Received: by gxk22 with SMTP id 22so1149233gxk.0 for ; Thu, 15 Oct 2009 10:14:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=JHMb40++rQg4K+MoCN3dZh0TEzBnTyCdRDWehqfi97Q=; b=IJ39YEwGc3S2rH6rIYhnXIwCBi0notio8j5GDy+WCobyZ+jd3omHiVi0BMMhan8rw0 abD9HE4Dau0jVaYEyOBgUw/9wb20as4YhOddYt3x1NvnVoVlDsWonlZ+iBeLp9MuvQ3L aVq0MuohXUSP0hPVN/Fa8DmyOeoab4gp60zqo= 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=QHI844AiyINUygFjxNxjwuBGO4po0UZ5txPhTBVIY5/5gy8ghnt4O2ulSo2YgZH9l1 Sf10EFFnTF6nAAFKVXleVYLA51CebAN3+91S4yBbsoiqE5L+eHbBIp9GU/r+Y1VLFPoO E3FkrHFTrnkPIW3ThUOVE+EBmv4oYB14b2vVU= MIME-Version: 1.0 Received: by 10.91.144.16 with SMTP id w16mr387406agn.21.1255626852620; Thu, 15 Oct 2009 10:14:12 -0700 (PDT) In-Reply-To: References: <4db64d890910140128m51edcae5o8e8871cc29523ce5@mail.gmail.com> <4db64d890910142141q2fa88340j8f7fc2da56b5275e@mail.gmail.com> <4db64d890910150056s3ac6ef35g448d6fe797c50137@mail.gmail.com> <4db64d890910150251h74079ab6jf0a733c3190ebc40@mail.gmail.com> <4db64d890910150259o1ba9ba54lf516950c998626a8@mail.gmail.com> <4db64d890910150918l2701e07difc21c223285fdeb7@mail.gmail.com> Date: Thu, 15 Oct 2009 10:14:11 -0700 Message-ID: Subject: Re: ESME-26 The message parser should ignore # in urls From: David Pollak To: esme-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e646079c8559950475fc6882 X-Virus-Checked: Checked by ClamAV on apache.org --0016e646079c8559950475fc6882 Content-Type: text/plain; charset=UTF-8 On Thu, Oct 15, 2009 at 10:09 AM, Richard Hirsch wrote: > OK - what do we have to do to solve the problem? Rewrite the parser? > I'm not sure. I think there are a couple of things... first, we can write some unit tests for the elements of existing parser and see how it's failing for particular cases and if there's something that can be done. If that doesn't work, we can change from stream of characters to a stream of bytes. Most of the existing parsing logic should work (or be easily ported), but we'll have finer control over the byte-streams for non-western character sets. > > D. > > On Thu, Oct 15, 2009 at 7:00 PM, David Pollak > wrote: > > 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 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 > 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 > > > -- 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 --0016e646079c8559950475fc6882--