ajack schrieb: > Stan Jordan [mailto:[EMAIL PROTECTED]] wrote: > > Subject: style="document" rulz! > > And style="rpc" sucks! > > To learn why, read this... > > http://www.fawcette.com/xmlmag/2002_04/magazine/departments/endtag/ > > The author presupposes that having two applications "work" when they get out > of synch is a good thing. I'd call that "silently failing". Personally, I'll > accept if my HTML is presented quite as the remote author intended, but I'm
But you dont want your browser to break because the author decided to move a table from the top to the bottom. And you certainly dont want to recompile your browser for each new website. > not so sure I'd like my banking application (or insert any business use > here) be so "tolerant" to miscommunication. > > Since WSDL allows for explicit & communication of the new interface > (hopefully commented with version changes, but fat chance I know since WSDL > is typically computer generated) I'd rather things break and I get the > chance to re-evaluate. That -- and/or preserve the old interface, and allow > the new interface for new clients. XML is not some magic glue that > understands when things change. It might still allow a non-validating [or > even validating, if remote schema] parse, and XPath may still access > elements, but the application will not understand the change, and that could > be very bad. I think what Adam Bosworth is saying is that there are 2 completely different use cases for SOAP. One being "just_another_corba" travelling through firewalls. The other one (with far more potential) is loose coupling of federated systems. And the key to loose coupling is weak typing (besides asynchronous messaging). Strong typing is nice for compile time checking of single process apps and RPC, but it gets in the way of building loosely coupled federated systems. Loosely coupling requires getting the type information (and other meta data) dynamically at runtime which DOM provides only partially but which could very well be supplemented by WSDL. But currently with most SOAP implementations WSDL only serves as a corba-like interface repository being used at compile time to generate stubs. And these stubs in turn lead to tight coupling. > > Also -- having spent the last N hours trying to get "document style" to work > I sure like the simplicity of explicit "tight" RPC. :-) as do I for cases requiring it. Just my 2 cents Guido > > regards, > > Adam >
