Why .NET WebServices are Better

Friday, July 11, 2003

Steve Maine's comments about the Java WebServices implementations are quite informative. Apparently, since Sun's spec is RPC, not doc/literal, doing any doc/literal webservice stuff locks you into an app server... guess its not too much different than doing anything else cool with Java... "Write once, run anywhere (as long as they have the same app server as you)".

6 Comments

I thought WebServices were for interoperability anyway, so why would it matter what app server you're running on? Don't you already know ahead of time what type of app server you'll be developing for?

HumanCompiler - Friday, July 11, 2003 1:05:00 PM
It wouldn't matter for the consumer, just the provider. So, it isn't a big deal, unless you decide to switch app servers or are creating a product that has some doc/literal webservices that it provides and it needs to be able to run on different app servers.

Jesse Ezell - Friday, July 11, 2003 1:25:00 PM
how is this better in .NET? you're still "locked into" an app server in ASP.NET.. it's called Windows.

Stu - Thursday, July 17, 2003 9:50:00 AM
.NET webservices are developed on .net platform are easy to develop in comparison to other platforms.Also they are easy to deploy

biswatosh samal - Monday, January 19, 2004 12:07:00 PM
The XML support and the common language runntime

(CLR) makes the web services easier.xml is supported by many platforms.

ramesh krishnan - Thursday, January 29, 2004 6:45:00 AM
Web Services provide a new level of interaction to all kinds of applications.The

ability to access and use a remote Web service to perform a function within an

application enables programmers to quickly deliver a more sophisticated applications

in less time.

Madhu Sudhan Reddy - Sunday, February 8, 2004 10:52:00 AM

Comments have been disabled for this content.