« RESTful robots |
| It WAS(n't just) me: Extend Your WCF Services Beyond HTTP With WAS »
Posted at 08:09 AM in .NET, Distributed Applications, Interoperability, WCF / Indigo, Web Services specs & more | Permalink
TrackBack URL for this entry:http://www.typepad.com/services/trackback/6a012876b389bb970c012876c21e2a970c
Listed below are links to weblogs that reference Why wsDualHttpBinding is not for interoperability:
You can follow this conversation by subscribing to the comment feed for this post.
The comments to this entry are closed.