By alashcraft
via devx.com
Published: Oct 23 2009 / 20:38
Web services can be very useful for integrating standalone components that communicate across a network. When used with straightforward call/return scenarios involving a very limited number of data types, setting them up and getting them to work is trivial. Because web services are standards-based, mixing .NET and Java technologies with them is also easy, which leads some people to believe that web services are the answer to the question of Java/.NET interoperability. They often are not.
Comments
nikki9696 replied ago:
The article raises good issues, but either I can't read or no alternative, real solutions were provided. Am I missing something?
mknutty replied ago:
Yes. Look who wrote the article. I thought the same till i paged down. LOL.
nikki9696 replied ago:
I did see that, and was hoping the article was more than marketing for his components. Give us a little hint or something.
mknutty replied ago:
There really isn't anything. I think there is one other vendor who has the same functionality. I think he was avoiding to directly pimp his product.
Voters For This Link (13)
Voters Against This Link (3)