[
Lists Home |
Date Index |
Thread Index
]
Still mystified by this thread.
I think before one labels this a "best practice for a web service",
one might want to be sure this is actually how extant web service
systems work. Otherwise, a naive builder may be hitting their head
against the wall trying to duplicate that code.
The theoretical discussions of where an action should be cited in
the data are fun, but do any of the commercial systems work like that,
or is this an attempt to influence the way they do work?
If someone sent me a Request For Proposal with complete instructions
as to how my staff will process that, I'd decline to bid. If someone
sends me a request for a feature with instructions for how to
code that, I reply with the feature description and ignore the rest.
At the coarse level of the document transactions, that works.
I'm not sure I want the customer to be the orchestrator. In fact,
I'm certain I don't.
len
-----Original Message-----
From: Roger L. Costello [mailto:costello@mitre.org]
I feel like we are close to exhausting the issue of the best way to
design an XML message. Recall the 2 approaches we have discussed:
- Approach 1: should I colocate an indication of the desired action
with the part of the message that the action applies to, or
- Approach 2: should I separate the actions from the data?
I am hopeful that today we can come to an agreed-to best practice for
this issue. At the very least, I would like to ensure that both
approaches are completely understood, as well as the tradeoffs.
|
