Comments on: RESTful routes and prefixes with CakePHP http://cakebaker.42dh.com/2009/04/22/restful-routes-and-prefixes-with-cakephp/ baking cakes with CakePHP Tue, 16 Mar 2010 17:17:53 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: cakebaker http://cakebaker.42dh.com/2009/04/22/restful-routes-and-prefixes-with-cakephp/comment-page-1/#comment-126184 cakebaker Thu, 23 Apr 2009 16:01:38 +0000 http://cakebaker.42dh.com/?p=1169#comment-126184 @Brendon, Martin: Thanks for your comments! @Brendon: Yes, I checked the 1.3 branch, but the behavior there is the same. And so opened an enhancement ticket for it. Personally I think only "/example" should be supported, because all "normal" routes start with a slash and with a prefix you simply put something in front of those "normal" routes. @Martin: Good point. I think the term "prefix" is ambiguous in this case, its meaning can be a path prefix (that's how I interpreted it), or as a name prefix like in your example. So maybe there should be two different "prefix" options... @Brendon, Martin: Thanks for your comments!

@Brendon: Yes, I checked the 1.3 branch, but the behavior there is the same. And so opened an enhancement ticket for it.

Personally I think only “/example” should be supported, because all “normal” routes start with a slash and with a prefix you simply put something in front of those “normal” routes.

@Martin: Good point. I think the term “prefix” is ambiguous in this case, its meaning can be a path prefix (that’s how I interpreted it), or as a name prefix like in your example. So maybe there should be two different “prefix” options…

]]> By: Martin Westin http://cakebaker.42dh.com/2009/04/22/restful-routes-and-prefixes-with-cakephp/comment-page-1/#comment-126126 Martin Westin Wed, 22 Apr 2009 18:00:28 +0000 http://cakebaker.42dh.com/?p=1169#comment-126126 Nice tip. That is exactly the kind of thing that can keep you guessing for an hour before going through the source. Thanks for possible saving me some time in the near future. I was just looking at Cake's REST chapter today. There might be a point to have the prefix just concatenate. It lets you create prefixes like example_posts. I'm not sure I would use that kind of url but... Nice tip. That is exactly the kind of thing that can keep you guessing for an hour before going through the source. Thanks for possible saving me some time in the near future. I was just looking at Cake’s REST chapter today.

There might be a point to have the prefix just concatenate. It lets you create prefixes like example_posts. I’m not sure I would use that kind of url but…

]]> By: Brendon Kozlowski http://cakebaker.42dh.com/2009/04/22/restful-routes-and-prefixes-with-cakephp/comment-page-1/#comment-126117 Brendon Kozlowski Wed, 22 Apr 2009 16:02:34 +0000 http://cakebaker.42dh.com/?p=1169#comment-126117 I know you and CakePHP's trac have a varied history, but have you checked to see if 1.3 has the same outcome, and thought of possibly creating an enhancement request? I would imagine that `/example`, `/example/`, `example/`, and `example` should all work the same, and that the only forward slashes that would be necessary would be in multi-level prefix path...not that I could think of a reason where someone would want to invoke a multi-level prefix path though... I can see why the enhancement request might be taken to heart (it helps make development easier by not having to know ins-and-outs of exactly how to set something up), but on the other side, CakePHP is about convention over configuration - even if this is a configuration, it follows a convention. It can't hurt to try, I suppose. ;) Thanks for documenting this, Daniel. I know you and CakePHP’s trac have a varied history, but have you checked to see if 1.3 has the same outcome, and thought of possibly creating an enhancement request?

I would imagine that `/example`, `/example/`, `example/`, and `example` should all work the same, and that the only forward slashes that would be necessary would be in multi-level prefix path…not that I could think of a reason where someone would want to invoke a multi-level prefix path though…

I can see why the enhancement request might be taken to heart (it helps make development easier by not having to know ins-and-outs of exactly how to set something up), but on the other side, CakePHP is about convention over configuration – even if this is a configuration, it follows a convention. It can’t hurt to try, I suppose. ;)

Thanks for documenting this, Daniel.

]]>