> Can you tell me the fundamental differences between Remoting and Web > Services? Why would you prefer to use one over the other? Is one a sub-set > of the other?
Yah, it's a bit confusing, why they didn't call it Net services I don't know. Probably IBM didn't want people to think it was ".Net" services :) Anyway, what we usually refer to as Webservices with SOAP being delivering through HTTP is built with the aspirations of cross-plattform distributed computing. Therefore we have stuff like UDDI for looking up services, restrict ourself to HTTP even though it's bad performance etcetera. Webservices are good for building webservices that's widely consumable, discoverable and sellable. That's their whole point. Then we have what Microsoft referes to as "Web Services Anywhere" and here's where the confusion as it uses .Net remoting and can be delivered through a number of different formats. Remoting is immensly more complicated with objects being passed forth and back, security contexts, leases, formatters, channels and whatnot. It seems a bit confusing that Web services can be delivered *through* remoting since it defeats the whole purpose of webservices, and still be called *web* services. But remoting is certainly the way to go if you're not building a service that you want to sell or that anyone should be able to access but instead want to sew together your own controlled enviroment. Then remoting offers better performance, security, features and a truckload of other stuff. PS. I've written a very introductional article about webservices up at http://www.existic.com/aboutwebservices.exc if anyone's feeling confused about the subject. best regards ---- #Mattias_Konradsson {web:www.existic.com} "Existic at your service" You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
