D
David Straley
Hi,
Would anyone make an architectural suggestion to me?
I'm building a web service which will query a DB and return several records'
worth of data. I want to receive that dataset at the client and decode it and
be able to access the individual fields randomly. I'm looking for a solution
where the clients do not have to be .NET clients.
I've thought that the best way to do this was to query SQL Server, and pull the
data out as an XML string (i.e. "FOR XML" in SQL Server), and then simply return
ONE LONG STRING to the client. Then on client side, parse up that string using
the DOM, etc. so as to get at my returned data.
However ... I'm asking for help... is there a better way?
Thank you for all help,
David Straley
Would anyone make an architectural suggestion to me?
I'm building a web service which will query a DB and return several records'
worth of data. I want to receive that dataset at the client and decode it and
be able to access the individual fields randomly. I'm looking for a solution
where the clients do not have to be .NET clients.
I've thought that the best way to do this was to query SQL Server, and pull the
data out as an XML string (i.e. "FOR XML" in SQL Server), and then simply return
ONE LONG STRING to the client. Then on client side, parse up that string using
the DOM, etc. so as to get at my returned data.
However ... I'm asking for help... is there a better way?
Thank you for all help,
David Straley