Lists Home |
Date Index |
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?
From: Rich Salz [mailto:firstname.lastname@example.org]
>... 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
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?