[
Lists Home |
Date Index |
Thread Index
]
1/10/2002 8:51:30 AM, "Roger L. Costello" <costello@mitre.org> wrote:
>
>
>Any other "best practices"? /Roger
In my humble and non-expert opinion, you hit exactly the right points.
Paraphrasing slightly,
XML web services usually have to be defined at a coarser granularity
than ordinary software objects;
When the transport may be slow/ unreliable or the processing complex/
long-running, consider an asynchronous coordination model;
Don't optimize until you know where the bottlenecks are, i.e., don't
assume that XML's "bloat" or HTTP's limitations are a problem until
they are demonstrated in YOUR application.
Maybe I'd add one more ...
Just say "no" to vendor-specific drugs!
The whole POINT of XML web services is to leverage Web
standards and experience with them to maximize interoperability, so be
wary of hiding the core technology behind too many protocols
and libraries and wizards.
|
