On Mon, 2004-02-16 at 15:47, Jan Hoskens wrote: > > I prefer to see the the continuation ID's in the URL. I see the > > continuations as resources existing on the server (temporary resources > > then), and a resource should be addressed by an URL. > > > > The URL-structure I'm currently using is as follows. Suppose the thing > > we're editing is an "order", then I would have the following URL's: > > > > /orders/<order-id> : displays the order > > /orders/<order-id>/edit : start the flow for editing > > /orders/<order-id>/edit/<continuation-id> : continue the editing flow > > /orders/new : creates a new order > > (flow then continues at /orders/new/edit/...) > > /orders : display list of all orders > > > > the paths can of course be prefixed by whatever you like (like an > > application and language identifying part). > > > > Note that I don't use (and don't need to use) the ".continue" part after > > the continuation-id. > > > > Well it's just a matter of taste, isn't it? As long as you pass your > continuation-id and catch it at the right place in your sitemap, there won't > be any problem.
If you're following an "as long as it works its fine" attitude, yes. The fact that resources should be identified by URL's is basic web architecture though. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
