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

Web Services Best Practice (was: Interesting XML-DIST-APP thre

  • To: "'xml-dev@l...'" <xml-dev@l...>
  • Subject: Web Services Best Practice (was: Interesting XML-DIST-APP thread)
  • From: "Bullard, Claude L (Len)" <clbullar@i...>
  • Date: Thu, 10 Jan 2002 08:44:11 -0600

coarse grained message
Take the frequency of the message type into account.  A coarse 
grained message is typically large.  A high rate of requests 
might suggest that you load some of that back to the client 
where possible.   There is a concept called "occasionally 
connected" in which a client has a copy of the data and 
most of the at-point-of-entry validation logic.  This 
proves useful in our business in field reporting applications 
in which the update does not need real-time or even near 
real-time access.  One has to step back and analyze the 
characteristics of the enterprise itself (nested processes, 
linear and non-linear processes) to find out if the 
paradigm of occasionally-connected works.  The environment 
affects this; for example, unreliable cell phone connections.

Orchestration/Choreography accounts for timing of events, 
intensity of events, duration of events.  Music or dance, 
the dancers should not fall on their butts because the 
drummer suddenly decides to reverse the syncopation.

len

-----Original Message-----
From: Roger L. Costello [mailto:costello@m...]

I started this discussion on the other list and have been truly
fascinated by its flow.  Thanks everyone!

I have been trying to summarize and organize in my mind all of the
discussion.  It seems to me that the discussion is leading towards a
"best practice" for using XML messaging (i.e., SOAP):

1. Stay away from using XML messaging to do fine-grained RPC.  For
example, stay away from a service which returns the square root of a
number.  Stay away from a service that returns a stock quote (this is
the classic-cited example of a Web service).

2. Conversely, use course-grained RPC.  That is, use Web services that
"do a lot of work, and return a lot of information".

3. Consider making the XML messages asynchronous.

4. Always take the overall system performance into account.  Don't
fine-tune your XML messaging when it consumes a small percentage of the
overall system time.

Any other "best practices"?  /Roger

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.