Re: url styling

>From a REST perspective, I think the best would be to make the action part of the query string. However, I also know not everyone agrees with this, so don't take my word for it. -- Filipe On Aug 10, 6:21 am, james_027 <[EMAIL PROTECTED]> wrote: > hi, > > is there any advantage or disadvantage

Re: url styling

[RESTafarian zealotry follows: you have been warned. ;-) ] james_027 wrote: > is there any advantage or disadvantage or best practices in forming > urls? Yes, there is. By following web architecture principles, as formalized in the REST (REpresentational State Transfer) methodology, you gain

Re: url styling

On Aug 9, 2007, at 10:21 PM, james_027 wrote: > > hi, > > is there any advantage or disadvantage or best practices in forming > urls? like which set are much better? > > domain/employee/1 > domain/edit_employee/1 > domain/inactive_employee/1 > > or > > domain/employee/1 > domain/employee/1/edit/

Re: url styling

I think the second is better because you're being consistent in your hierarchy order. IE you're going from least specific to most specific: domain -> object -> instance ->action Instead, in the first one you're going: domain -> action -> object -> instance Then again, it's purely preference.

url styling

hi, is there any advantage or disadvantage or best practices in forming urls? like which set are much better? domain/employee/1 domain/edit_employee/1 domain/inactive_employee/1 or domain/employee/1 domain/employee/1/edit/ domain/employee/1/inactive/ thanks james