RE: Exposing resources/services vs hiding implementation detai
Pardon my density. I don't quite get this. 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)? So then, ostensibly, the discovery service keeps a list of services that all have one URI, somewhat like calling the PBX operator to get a line into a business? len From: Rich Salz [mailto:rsalz@d...] >... the extreme of providing a >single poiunt of access (e.g. http://foo.org/myService ) to POST >everything to just doesn't seem to cut it when it comes to scalability >and integratability. How so? I can see why the single point is better for integration -- you only change one message posted to one URL, as opposed to one message posted to "n" URL's -- not worse. And I don't see the difference in scalability at all. Can you explain?
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format