I'm looking for some general guidelines/advise on the best way to represent data sets that will be passed to web service consumers. For example, how should a data set be represented so that it can be passed from a .Net provider to a Java-based consumer? Obviously, the serialized object should be as light-weight as possible. A .Net DataSet is not lightweight, has a lot of functionality that is not required strictly for passing data and a Java-based consumer doesn't intrinsically know what a DataSet is.
What are some general guidelines for determining the practical limit for the amount of data (think rows of data) that can be returned in a timely fashion. I realize that this is a very subjective assessment but I'd be interested in getting a feel for when passing a large block of soap/xml becomes impractical from a performance standpoint. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: >>> Error in line 15 of ADVANCED-DOTNET.MAILTPL: unknown formatting command <<< -> .NET Architecture and Design: Designing Distributed Applications with <-
