Rob Eamon wrote: > From an SO perspective, when will the URI of a service operation be > directly exposed to a user of a UI? Won't URIs predominantly be used > at design-time and/or as a configuration item for the UI app, at > least at the entry level of the service (UI calls an operation using > configured URI to start, then calls other operations using URIs > returned by that and subsequent operations)? UIs aren't part of the > service, correct?
What this assumes is that you will always get the work flow right the first time and that there are not any desirable variations on how the work flow might be better facilitated for certain circumstances. For me, a service is something that exposes resource that are of interest to a work flow. That work flow is something that a client implements. With HTML web pages, we provide some choices of possible work flows through hyper links. Have you ever pushed the "Back" button on your web browser? That indicates that the "service" did NOT provide you with the right work flow. Gregg Wonderly
