On Sun, Apr 6, 2008 at 11:51 PM, Damjan [EMAIL PROTECTED] wrote:
Previously, Routes used a ';' mark for an action in map.resource, like:
/comments/4;preview
With 1.8, its now:
/comments/4/preview
What exactly is the reason for this?
I'm asking since ; seemed like a nice
Hi,
I don't know the real reason behind this change but for me it feels
more natural and elegant to have clean URLs with slashes than using
any other caracters =)
Blaise
On Apr 6, 11:51 pm, Damjan [EMAIL PROTECTED] wrote:
Previously, Routes used a ';' mark for an action in map.resource,
I don't know the real reason behind this change but for me it feels
more natural and elegant to have clean URLs with slashes than using
any other caracters =)
well the difference is between
/some_resource;edit
/some_resource;preview
etc.
and
/some_resource/edit
now /edit looks like an
On Apr 7, 2008, at 7:03 AM, Damjan wrote:
well the difference is between
/some_resource;edit
/some_resource;preview
etc.
and
/some_resource/edit
now /edit looks like an aditional resource... ;edit otoh looks like a
special view of the resource
Using ; was actually a no-no according to the
maybe because of this:
http://www.issociate.de/board/post/11276/Forwarding_URL_with_semicolon.html
although I don't think Apache is doing the correct thing there... I'll
check that later
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
I'm releasing Routes 1.8 today, it has a few fixes for some unicode
bugs, but the main reason for the announcement is that how
map.resource works is being altered in a way that may break hard-coded
links.
Previously, Routes used a ';' mark for an action in map.resource, like:
yay!
iv wondered every day this week when you would release :)
On Fri, Mar 28, 2008 at 9:10 PM, Ben Bangert [EMAIL PROTECTED] wrote:
I'm releasing Routes 1.8 today, it has a few fixes for some unicode
bugs, but the main reason for the announcement is that how
map.resource works is being
