Phew.
This doesn't do much increase my liking of the webservices bandwagon....

• Interoperability appears to be poor to sorry, not to mention wrapped in thick layers of hard to understand issues of RPC vs. literal encoding.

• Calling a method requires all the parameters to be named (that's OK) and in a given order (way less than OK in my book)

• The field is already strewn with horribly complex message formats (e.g. ADO.Net datasets) that force you to either reinvent client side behavior OR to use a Microsoft client. (How is this supposed to be good? Document/literal advocates in the "webservices are about document based messaging, not RPC" field say it is, but this forced separation of data and behaviour looks a gigantic leap backwards to me)

Ok, I got it off my chest. Now let the flamethrowers be unsheathed.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.