NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
RSS and NNTP
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
And the news was...? (Score:2)
This largely describes "web services" in general.
Well, I've seen three kinds: (1) toy examples, (2) wrapping of propietary protocols into XML (they will still be closed and proprietary, mind, as long as the vocabularies and protocols are not public), and then these (3) pointless rewrappings of existing protocols/frameworks.
In (2) and (3) the only measurable effect has been manifold increase in bandwidth, and the need to have an XML parser everywhere. Not to
Re:And the news was...? (Score:3, Informative)
There are a few benefits to Web Services, like the reinvention of IDL and "baked in platform neutrality", but there were better ways to get those benefits than XML-RPC, SOAP, WSDL, and RWSA(*) provide. For example, wrapping a proprietary protocol in XML makes it easier to deal with an existing system in 12 different programming languages without multiplying the number of buggy implementations of the existing protocol. Whether or not support for 12 or even 2 new languages is necessary or desirable is an exercise left for the reader.
The other major benefit to Web Services is that it's a visible, neutral RPC protocol. They're not especially good RPC protocols, but at least you can stop worrying about the bits on the wire when developing services (at least until you see how many bits are going on the wire).
*: Random Web Services Acronym
Reply to This
Parent