Cart
[Home] [By Thread] [By Date] [Recent Entries]
Tom Scola wrote, > Every RPC API I've ever used has made network programming > *more* difficult in the long run, since they obscure network > connection and timeout problems. These problems will > probably outweigh the 2 man-days of development time you > thought you saved by using SOAP. Agreed ... The critical issue for any RPC mechanism whatsoever (SOAP, IIOP, RMI, DCOM etc.) is that, unlike local calls, remote calls can fail. That means there'll always be a conflict between transparency (making remote calls look like local calls) and recoverability (dealing with network failures *as* network failures rather than as failures at the application-level). FWIW I don't think anybody knows how to address this problem yet ... tho' some of the things that the Aspect Oriented Programming people are doing look promising. SOAP, to it's credit, doesn't seem to be pushing too hard in the transparency direction ... I think that's probably the right choice. Cheers, Miles -- Miles Sabin Cromwell Media Internet Systems Architect 5/6 Glenthorne Mews +44 (0)20 8817 4030 London, W6 0LJ, England msabin@c... http://www.cromwellmedia.com/ *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
