- Original Message -
From: David Corbin <[EMAIL PROTECTED]>
Date: Tuesday, June 20, 2006 0:24 am
Subject: Re: [Jruby-devel] A strategy for Mongrel.
To: jruby-devel@lists.sourceforge.net
> On Monday 19 June 2006 07:24 am, Ola Bini wrote:
> > Actually, I'm not sure tha
On Monday 19 June 2006 07:24 am, Ola Bini wrote:
> Actually, I'm not sure that performance is the big issue in HTTP parsing,
> but google for a few interviews with Zed, and you will notice immediatly
> that he talks much about the security in a parser generated from a formal
> description instead o
From the scm repository at Rubyforge.org
http://rubyforge.org/plugins/scmsvn/viewcvs.php/trunk/ext/http11/http11_parser.rl?root=mongrel&view=log
Scott
On 6/19/06, Danny Lagrouw <[EMAIL PROTECTED]> wrote:
Ola,The JavaCC (Compiler Compiler) should be able to create a parser basedon BNF. I'd look
Ola,
The JavaCC (Compiler Compiler) should be able to create a parser based
on BNF. I'd look into it, but the http11_parser.rl file is not
included in the gem file. Any idea where I could find it??
--
Danny Lagrouw ([EMAIL PROTECTED] )
Read my blog: http://blog.dannynet.net
On 6/19/06, Ola Bin
Actually, I'm not sure that performance is the big issue in HTTP parsing,
but google for a few interviews with Zed, and you will notice immediatly
that he talks much about the security in a parser generated from a formal
description instead of hand crafted code. According to him, it seems his
p
What am I missing? HTTP parsing is trivial? I can't imagine why generated
code is need, or that it could be a signifcant factor in performance.
On Monday 19 June 2006 04:00, Ola Bini wrote:
> Hi,
>
> I've been peeking at Mongrel again, trying to figure out the best way to do
> this. There are
