Cart
[Home] [By Thread] [By Date] [Recent Entries]
Rich, On Tue, Apr 05, 2005 at 04:25:13PM -0400, Rich Salz wrote: > >Is this approach (a single URI) a means to unify multiple > >services under one dispatching service (eg, receives the > >message, reads it, determines who should do the work, > >sends that on with details)? > > Yes. > > Having everyone from the outside come in through a single door has its > benefits. Maybe not for everyone, and not all the time, but you can't > just dismiss it. Which door would that be, the URI or the TCP port? 8-) I think the benefits to a single URI are few when compared with the benefits of having many (well, one per resource anyhow 8-); improved visibility being the biggie, but you also have the opportunity to use hypermedia, even in a POST-only app. e.g. POST a document, get one back with a different URI to which you have to POST another document, etc.. You're also well positioned for exposing the data behind those URIs in the future, simply by implementing GET on them. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
|
