Re: Recordset conversion to xml

My 2c
I would say webservices only.. It's just one extra method on the
recordset object which u invoke to receive an xml string representing
itself.
This keeps existing COM object interaction and code with the Recordset
easy to manage and more flexible ito other integrations (e.g. ASP)
If you want to transport Recordsets over SOAP, sending the xml-recordset
can be interpreted by the consumer according to its needs or use a
typemapper to achieve a transparent xml->recordset transformation.

And maybe the recordset will one day become a standard data type like
the int across business processes over various platforms? :)


-----Original Message-----
From: Mark A. Gregory [mailto:[email protected]] 
Sent: Wednesday, July 31, 2002 1:40 PM
To: [email protected]
Subject: [SOAP] Recordset conversion to xml


We have a conundrum.

Were converting an application to a business logic layer and a Web
Service layer. The Business logic layer generally outputs recordsets
from the COM+ Interface functions.

Should we convert the recordset outputs to xml in the com+ components or
do this in the Web Service Layer?  If we do it in the Web Service does
this put extra load on the server that would be better moved to the COM+
layer?

Thank you
Mark

You can read messages from the SOAP archive, unsubscribe from SOAP, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.