Re: Optimizing webservice call which are returning datasets
- From: "Marc Gravell" <mgravell@xxxxxx>
- Date: Mon, 13 Feb 2006 15:28:37 -0000
OK, scratch that idea then... it was worth a shot.
Beyond that... my only real advice in this scanario is to minimise what you
are transferring... are there any columns with lots of text in them that the
client doesn't need? Do you really need all the rows or could you use
paging? That sort of thing.
Your original post doesn't give any indication of what sort of size /
complexity of DataSet we are talking about; if this is returning 15
DataTables (with complex relations) each with 40 columns and 10000 rows then
yes, it will take a while. If you genuinely need all of the data at the
client (and you can't cache it locally for whatever reason) then I'm not
sure there are many alternatives under 1.1 and [WebMethod].
If you were in 2.0, you could consider using a GZip'd binary serialization
of the dataset transferred via MTOM (WSE3) - this should (theoretically)
take a lot less bandwidth. But according to the original post, you're not.
<stumped/>
Marc
.
- References:
- Re: Optimizing webservice call which are returning datasets
- From: Ken Cox - Microsoft MVP
- Re: Optimizing webservice call which are returning datasets
- From: sameer
- Re: Optimizing webservice call which are returning datasets
- From: Ken Cox - Microsoft MVP
- Re: Optimizing webservice call which are returning datasets
- From: sameer
- Re: Optimizing webservice call which are returning datasets
- From: Marc Gravell
- Re: Optimizing webservice call which are returning datasets
- Prev by Date: XmlNode to XmlDocument question.
- Next by Date: Re: Webservices called from behind proxy server fails
- Previous by thread: Re: Optimizing webservice call which are returning datasets
- Next by thread: I thought I heard that v2 would allow a WebService to return a DataTable
- Index(es):
Relevant Pages
|