| Subject: avoid returning dataset |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/23/2008 6:11:17 PM |
| From: =?Utf-8?B?S2V2aW4=?= [Email Address Protection] |
hi all, what's the alternative to return a dataset/datatable that is dymanically populated from dymanic sql? remember the number of column is known only at runtime. thx Kevin |
| Back |
| Subject: Re: avoid returning dataset |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/24/2008 1:20:23 AM |
| From: "Marc Gravell" [Email Address Protection] |
As always, it depends on what you need ;-p But for a simple answer - how about csv/tsv.... most clients will have a mechanism of dealing with that? Or xml? Or if large, a Stream of the same (note this is only really effective using transport security; with message security it needs to buffer everything anyway; better-still with MTOM etc). If your transport doesn't already include it, you might [again for large data as a Stream] consider throwing a GZipStream into the pipeline so you have a compressed MTOM stream of a simple data format). Marc |
| Back |