Doing web service design obviously you have to consider the trade-off between coarse versus fine grained methods and the number of roundtrips.
We, for example, implemented a relative small number of methods which return large amounts of data (with the possibility to filter) in order to reduce the number of roundtrips to the server. This works in general fine. However doing so you can run into problems with errors. What if one of the parts of the data returned fails. Does the whole function generate an exception? Or is the part that cannot be returned empty? etc. Stephan > -----Original Message----- > From: Ronald H�tter [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 23, 2002 10:40 PM > To: [EMAIL PROTECTED] > Subject: Design guidelines for web service interfaces? > > > Does anybody know about some guidelines on how to design web > service interfaces? I'm facing a couple of problems when > translating object oriented interfaces into traditional > RPCs. > Thanks, Ronald >
