Brian,

>Here an example scenario: suppose I have a web form that currently uses a business object, "boSomeBizObj", to get and save a dataset. The user modifies some of the data, posts back, binds back the data, and calls "boSomeBizObj.SaveDataSet()" to update the data. If I now want to modify the architecture so that I can expose that same functionality as a web service, what would be a good way to engineer this? Would I perhaps have a web service that takes the data (indluding mofications, somehow) as XML, translates it into a DataSet, then instantiates "boSomeBizObj" and passes the dataset to a call to SaveDataSet()?

There is a new Web Services Jump Start in version 1.1. Regarding saving data the approach you've mentioned is a good one. Regarding security, I recommend checking out the article "WS-Security and Remoting Channel Sinks Give Message-level Security to your SOAP Packets" in the November 2003 issue of MSDN Magazine. At the beginning of this article there are links to related articles on WS security:

"Programming with Web Service Enhancements 1.0 for Microsoft .NET" - http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/progwse.asp

"Remoting Example - Channel Sink Provider"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconremotingexamplechannelsinkprovider.asp

Regards,