On 11/30/06, Steve Jones <[EMAIL PROTECTED]> wrote: > So as a follow-up question ( I'm learning something today!) . Would > the prefered approach be > > http://www.frood.com/customer1 > http://www.frood.com/customer2 > > or > > http://www.frood.com/customer?customerId=1 > http://www.frood.com/customer?customerId=2 > > Or are both considered the same? The former could be quickly created > from a URI re-write of the latter of course, but I'm just wondering > what was the difference, I'll be honest the REST bit I'm writing at > the moment is using the later approach, so it would be good to know if > it isn't REST.
>From a REST POV, they're basically equivalent. But there are other considerations. For example, using the first option you couldn't direct a client to those resources using an HTML form, since HTML forms only parameterize using "?". As an architectural style, REST is limited in the kinds of constraints it can define; if it's not a constraint on a relationship between software architectural elements (data, connectors, components), it's not in play. That leaves lots of room for best practices which have nothing to do with REST. Mark.
