Cart
[Home] [By Thread] [By Date] [Recent Entries]
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
|
