Re: Recordset conversion to xml

Phil Troy <[email protected]>
Newsgroups gmane.comp.windows.devel.soap.general
Message-ID <[email protected]>
Dear Mark

Hi!

If I understand what you are trying to do, I would think that the best
approach is to get rid of the COM+ interface and go directly from the
client layer to the web services layer.  My sense is that com technology a)
just adds an extra layer without really giving you any value and b) is not
even the choice of technologies at Microsoft anymore.  

My sense is also that you should be careful about how you implement your
database.  I am a Delphi designer/developer but do not know the performance
of ADO (I am not a Microsoft fan and thus have doubts that ADO will perform
well if your traffic is even moderately heavy).  If you wish to stick with
a local database engine (which may have problems with multiple simultaneous
requests if not done correctly), you should probably design your system so
that you can convert it to work with a database server.  

Phil Troy

Philip M. Troy, Ph.D.
TROYWARE
[email protected]
[email protected] 

---------------

Message text written by Discussion of implementing SOAP applications today
> 
Are you thinking SOAP toolkit or .Net c# web service to convert the
recordset to
XML?  I would have thought that this would put an extra load on the web
service server?

The recordsets we create are using ADO within Delphi COM+ objects.

Mark


-----Original Message-----
From: Bryan Allott [mailto:[email protected]] 
Sent: Wednesday, 31 July 2002 9:53 PM
To: [email protected]
Subject: Re: [SOAP] 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.

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




----------------------- Internet Header --------------------------------
Sender: [email protected]
Received: from listserv3.develop.com (discuss.develop.com [63.111.243.44])
        by siaag1ad.compuserve.com (8.9.3/8.9.3/SUN-1.14) with ESMTP id
IAA29098;
        Wed, 31 Jul 2002 08:43:12 -0400 (EDT)
Received: from listserv3 (63.111.243.44) by listserv3.develop.com (LSMTP
for Windows NT v1.1b) with SMTP id <[email protected]>; Wed,
31 Jul 2002 5:42:53 -0700
Received: from DISCUSS.DEVELOP.COM by DISCUSS.DEVELOP.COM (LISTSERV-TCP/IP
          release 1.8e) with spool id 2134217 for [email protected];
          Wed, 31 Jul 2002 05:42:52 -0700
Received: from juneau.gt.com.au (203.62.159.98) by listserv3.develop.com
(LSMTP
          for Windows NT v1.1b) with SMTP id
          <[email protected]>; Wed, 31 Jul 2002 5:42:51
-0700
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SOAP] Recordset conversion to xml
Thread-Index: AcI4CF9HLrZ/Uf4jQxGd5sUE7wDn9gAfqPJQAACUyVAAAY02oA==
Message-ID:  <[email protected]>
Date:         Wed, 31 Jul 2002 22:42:50 +1000
Reply-To: Discussion of implementing SOAP applications today             
<[email protected]>
Sender: Discussion of implementing SOAP applications today             
<[email protected]>
From: "Mark A. Gregory" <[email protected]>
Subject: Re: [SOAP] Recordset conversion to xml
To: [email protected]
Precedence: list

<

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.