How easy is it to provide soap-based access to a remote ADO Recordset?
There's a new generation of applications like Groove that are only
supporting SOAP for interprocess communication ("localhost soap"). Check
http://www.infoworld.com/articles/pl/xml/02/11/04/021104plgroove.xml and
http://www.groove.net/devzone/webservices/ for some details.
No DDE, OLE, ... Check it out.
Cheers,
Michael.
Quote:
> Why would you use Soap if the client and server are on the same machine?
> Soap introduced quite a bit of overhead converting the recordset into XML
> and back again. This overhead is acceptable is you need to cross
firewalls
> or transfer data between architectures but I don't se any advantage when
> you're running on the same box?
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> > Thanks Roger. I've checked out the sample and I need to think more
about
> > this.
> > In more detail ... I want changes in the clients-side (remote) recordset
> to
> > be reflected in the server-side recordset (and database) more or less in
> > real-time. This may sound wierd but physically the client and server
are
> on
> > the same machine.
> > Michael.
> > > There's an sample of using a customer type mapper for ADO recordsets
in
> > the
> > > SoapToolkit sample download.
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > > On the client, I would like to use plain old data bound controls
that
> > > access
> > > > an ADO Rescordset (including Update).
> > > > On the server, I have a fabricated in-memory ADO Recordset that I
want
> > the
> > > > client to access using soap protocols.
> > > > Is there anything that does this somewhat automagically specifically
> for
> > > ADO
> > > > Recordsets? ...or is it entirely roll-your-own.
> > > > (p.s. I'm familiar with ADO/RDS and want to avoid that).
> > > > --
> > > > Michael Herman
> > > > Parallelspace Corporation
> > > > Developers of Parallelspace eMail for Groove Workspace
