Saturday, September 07, 2002

Gordon's take on ADO.NET and Web Services The thing with doing web services is that the absolute biggest benefit, in my mind, is interop.  My employer has spent the last year putting a web service wrapper around our existing COM based application.  Out of the 4 early adopters I've worked with, 3 are using Java and Apache SOAP.  These are customers that we were previously shut out of because they refused to run Windows in their data center, and the Java-COM bridges out there were slow or buggy, or both.  Before you go slapping a [WebMethod] on their methods and start tossing DataSets out on the wire, ask yourself: why?  If what you build will operate only on a single platform, then why not use Remoting, or RMI, or some other method to do distributed computing.  If Interop is a problem with every other distributed computing platform.  I can't think of a reason for SOAP to exist.  Actually, I have another question about DataSets and remote interfaces.  Even if it would interop, do you really want to go exposing raw data sets out of your interface?  I'm not sure that this is a best practice in the first place.  [via Sam Gentile's Radio Weblog] 9:50:37 AM    comment [] Microsoft readies SharePoint 2.0 collaboration platform - it sounds like there will be an ASP.NET layer that will abstract CAML, which will definitely make the product wide open.  [via Sam Gentile's Radio Weblog] 9:46:36 AM    comment []

© Copyright 2005 Paresh Suthar. Last update: 8/19/2005; 3:21:59 PM. This theme is based on the SoundWaves (blue) Manila theme.