On Wed, Jul 31, 2002 at 08:23:19AM -0400, Newcomer, Eric wrote: > > One of the problems with this simplistic view of Web services is that it avoids the issue of mapping to the underlying executable programs that implement the Web services. [snip] This is exactly right. Of course if I had my way, there'd be no different types of mappings to worry about; every existing app would be encapsulated behind a component exposing a REST connector. But what ever your preference, I think we agree that having *one* approach is a good thing. If we say the WSA supports RPC and REST, then what sort of guidance is that to developers? Not much, I suggest. So while I agree with Mark that WSA should embrace REST, I don't believe that can be done without excluding other architectural styles. But for now, I'm happy to hear that more people are interested in integrating REST. Perhaps later it will become clearer to the group what this means. But please, for now, let's try to focus on the short-term deliverables; the requirements doc, and the SOAP+WSDL harvesting. MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. distobj@acm.org http://www.markbaker.ca http://www.idokorro.comReceived on Wednesday, 31 July 2002 11:59:01 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:03 GMT