Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.210.52 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:content-transfer-encoding;
        b=QvkbCez2b6NuG2sRbDp+0WSxEv+v/ffrCOHe96ZsLzmxT6wgCzrFoQYZ6s1OpS3IAh
         BEUVOd5FAaoufQwMkCNuMHHtRR/0ue8Ez5z03eWpd0dHmutjtSC7aqpIqDxCXOQ0xX3T
         nit8JV11cNaX/Reg0Q44zDwg1vqtiiWcYTN/s=
MIME-Version: 1.0
In-Reply-To: <AANLkTinEk6tqf2LSoQJJ12n86qi_zz60i+wqTcevjCuh@mail.gmail.com>
References: <AANLkTim6uyS9Sa3Yb3ta-RnFMSQPE18hRSSYi6kZXaDj@mail.gmail.com>
	<AANLkTikt-QwARF4ccjYnHAHtxjnkHK8MgbMNi=ywU9JV@mail.gmail.com>
	<AANLkTinf8QLp97TyKrmsr6izWjgbAoAa=L4azdA4y08T@mail.gmail.com>
	<AANLkTikaB1WfkCRnC5YNFv6tNV9uqfQfPoqNpfKF9CyM@mail.gmail.com>
	<AANLkTikvftdbkRBSWxdycQaN2aP=1VL7OY6sZVE04r39@mail.gmail.com>
	<AANLkTimyLW03tdo5xkKkH9dLv5bJASA+nSVRL076FA_e@mail.gmail.com>
	<739B8B5B-842A-4CC4-871C-2DC5B0616266@apache.org>
	<AANLkTi=jxq=vhtOnFwBsOBbTXF5srCBtB7KUPL09oVz+@mail.gmail.com>
	<D7756A48-1967-416D-BE27-7DFB0B63C786@apache.org>
	<AANLkTikuHfytRtwT9NADZZtCKd5N-r3_JcV-i2U4LUmJ@mail.gmail.com>
	<AANLkTinEk6tqf2LSoQJJ12n86qi_zz60i+wqTcevjCuh@mail.gmail.com>
Date: Thu, 19 Aug 2010 18:48:37 +0200
Message-ID: <AANLkTinVYVTsUZ2iCxWw6QHohGm+wNqAmfSjyxNmRQDQ@mail.gmail.com>
Subject: Re: Vhosting Requirements (was: Re: [jira] Commented: (COUCHDB-230)
 Add Support for Rewritable URL)
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 19, 2010 at 6:30 PM, Jason Smith <jhs@couch.io> wrote:
> On Thu, Aug 19, 2010 at 23:14, Benoit Chesneau <bchesneau@gmail.com> wrot=
e:
>
>> On Thu, Aug 19, 2010 at 5:56 PM, Noah Slater <nslater@apache.org> wrote:
>> >
>> > On 19 Aug 2010, at 16:49, Benoit Chesneau wrote:
>> >
>> >> Well asking without giving yourself some data make it irrelevant but
>> >
>> > Not really.
>> >
>> > I'm suggesting that if we're going to use performance as an argument, =
we
>> use data and not supposition.
>>
>> The way pattern matching works should explain by itself though ;)
>>
>
> AFAIK Erlang ships with Perl-compatible regular expressions written in C.
>
> re:compile()
>
Yes. so ?

> Anyway the whole performance argument is not relevant. Who cares? You are
> about to do a b-tree lookup from the hard disk. How much will regex vs.
> pattern match on a 20-byte string matter?

b-tree ? Where ?
>
> My point was, why are we inventing syntax out of our asses for every
> different situation? Regular expressions should be considered because:
>
> =A01. They match patterns

yes. Pattern matching too but we only match terms,  and they are
common in Erlang.

> =A02. They capture groups and can access them later

yes. who care ? A lot of urls rewriters are not using regexp because
it adds an extra layer of complexity: webmachine in erlang, werzeug in
python, ...

> =A03. Everybody knows them

that's not true. http://xkcd.com/208/


To answer to this "reinventing" . We had long discussions on how to
manage rewriting in couchapps. Some included "regexp", we fall in the
current system. Ie pattern matching because it was a lot easier to
understand and *simple*.  SInce the system is already in place, I
wanted to reuse it too, there is no need to have 2 dofferent ways to
handle rewriting.

I would like to keep it *simple*, that's the key.

Anyway, can we go back to the topic ? I still don't understand how
vhosts in 1.0.1 or in trunk are a problem ? About that I'm thinking we
could propse a request_handler that isn't relying to vhost at all and
make them an option, would it be ok ?