<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jan 20, 2008, at 1:33 PM, Thomas L. Shinnick wrote:</div><blockquote type="cite"><div> <font size="3">At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote:<br> <blockquote type="cite" class="cite" cite="">/class/search<br> /class/id/1111/view<br> /class/id/1111/update<br> /class/create<br></blockquote><br> <spew register="pedant"><br>One important topic in the book is that people mix 'verbs' into their URIs when they shouldn't, or at least when they don't _have_ to. Using the book's concepts your URIs would become<br><br> 1) GET /class?pattern=breadbox<br> 2) GET /class/id/1111<br> 3) PUT /class/id/1111<br> 4) POST /class<br> </spew></font></div> </blockquote><br></div><div>Clipped a bunch. This is great food for thought. I am missing in this scheme how you would know to serve the form for updating. That seems to be the real point of /class/id/1111/update. I suppose that should be /class/id/1111/edit instead and it would, if it could, properly PUT the form to /class/id/1111, yes?</div><div><br class="webkit-block-placeholder"></div><div>-Ashley</div><div><br class="webkit-block-placeholder"></div></body></html>