[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Web Services Best Practice (was: InterestingXML-DIST-APP t

• To: xml-dev@l...
• Subject: Re: Web Services Best Practice (was: InterestingXML-DIST-APP thread)
• From: Mike Champion <mc@x...>
• Date: Thu, 10 Jan 2002 11:12:22 -0500
• In-reply-to: <3C3D9C62.B4D4AE03@m...>

1/10/2002 8:51:30 AM, "Roger L. Costello" <costello@m...> 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.

• References:
  • Web Services Best Practice (was: Interesting XML-DIST-APP thread)
    • From: "Roger L. Costello" <costello@m...>

• Prev by Date: RE: Another strong/loose decision tree node (was Re: Interesting XML-DIST-APP thread)
• Next by Date: ANN: RDF to SVG tool
• Previous by thread: Re: Web Services Best Practice (was: Interesting XML-DIST-APP thread)
• Next by thread: Re: Web Services Best Practice (was: Interesting XML-DIST-APP thread)
• Index(es):
  • Date
  • Thread