I working on a design guide for publishing as a technical report sometime One thing you need to thing about is round trip times; a LAN scoped system can be chatty, but a long haul WS arch needs to deal with higher latency designs, for which a many-query design may not work. I like queries that can return a lot of info, same for any action reqs.
----- Original Message ----- From: "Jesper Söderlund" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 17, 2002 23:25 Subject: WebService interface design.. Since the whole WebService thing is quite new, to me at least, I wonder if one of you guys have seen any resources or have any personal tips on "gotchas" for how to design the web service interface to make them robust to change. I mean it's easy enough to smack together an interface but another thing to make the API robust. My feeling right now is that the web service paradigm encourages a quite "course" level of API and that the API should consist of some small query operations to retrieve adequate information and then a big "submit-the-whole-thing" API operation. Any ideas? /Jesper
