Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <47ABCD89.10400@anconafamily.com>
Date: Thu, 07 Feb 2008 22:33:29 -0500
From: Jim Ancona <jim@anconafamily.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Abdera Dev List <abdera-dev@incubator.apache.org>
Subject: Route matching too liberal?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have run into some problems with my Routes matching unexpectedly. 
Before filing a bug, I thought I'd ask for feedback on whether the 
current behavior is correct.

The current algorithm attempts to match the non-variable parts of the 
pattern, setting the variable to whatever is in between.

So the pattern "/base/:collection/" matches both "/base/test/" and 
"/base/test/123/". In the second case, the value of the collection 
variable is "test/123". In my opinion, not allowing matches to span URI 
segments would be less prone to unintuitive results.

FWIW, a quick glance at some docs on Ruby Routes seems to indicate that 
they do not span URI path segments.

Thoughts?

Jim