Elliot, In general, reducing functionality will raise interoperability issues - that observation applies to the deprecation of rpc/literal as well.
Given the two major style/usage combinations, i.e., rpc/encoded and document/literal, the latter seems to me a superior model mainly because all references to types are local (as intended, of course). I've swung much more in favour of document/literal especially after Axis 1.2 has strengthened its support for it. doc/lit of course decouples the request/response from a procedural model on the server side, which is nice and fine philosophically, but practically, doesn't affect me much. I suspect it doesn't affect many others as well, especially those persisting with rpc/enc services. As for the "hybrids", rpc/lit and doc/enc (yes, I know they're orthogonal combinations, not really hybrids), the rationale for using them has always been thin, so lopping them off in the newer standard seems fine. Yes, it hurts interoperability, but keeping 4 combinations around could have far worse longer-term consequences for web services as a whole - a classic case where the needs of a few must be sacrificed for the needs of the many. Anand On Wed, 18 Aug 2004, Elliot Metsger wrote: : Anand et. al, : : Can you offer your perspective on the interoperability of rpc/lit in the : future? Dosen't the WS-I Basic Profile 1.0 go a ways to reducing : opportunities for interoperability issues? : : Thanks, : Elliot (a ws newbie) : : Anand Natrajan wrote: : > Charles and Steve, : > : > Mostly for my curiousity, are you using an rpc/encoded service or a : > document/literal service? My information may be wrong, but I believe the : > latter doesn't support overloaded methods. Given that the web services : > world is moving to doc/lit, having overloaded methods may be ill-advised : > for future compatibility. : > : > Anand
