Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

SOAP 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I guess SOAP::Lite is as lite as SOAP is simple and object oriented.

      • That's a good one. And sad... :(

      • A number of years ago I did a presentation called "Why SOAP Sucks, Why SOAP Sucks!". At the start of it I had enough paper to contain all the specs required to fully understand SOAP (XML, SOAP, WSDL, UDDI, XML-Schemas, and possibly something else)... The entire thing comes to just over 1000 pages.

        Anyone who can understand all that and build an interoperable system deserves a medal. Sadly there is nobody who does.
      • Heh. Exactly my feeling :-)

        I gave up understanding why namespaces are called http://something/ [something] (apparantly Microsoft calls them http://tempuri/ [tempuri] by default). It doesn't point to anything, and it's generally confusing.

        • Because namespaces are URIs, and that in turn is because those are (generally) globally unique identifiers. That’s all. In the context of namespaces the URI doesn’t have any meaning beyond being a unique identifier. That’s fine, as URIs don’t have to be retrievable, even those with schemes you’re used to thinking of as retrievable, such as “http:”. You can use any other scheme though. For namespaces I like to use “tag:” when I don’t plan to put any

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.