Hi Dan,
A way to make it smaller that I use is deleting all the empty items which
are made by default.
(Than there must be of course be reasonable amount of empty items).
You have to check per item when it comes from the database on the
dbnull.value for that.
(Creating a new table before you do the writeXML)
When you read it back the item when it not exist is "Is Nothing".
Another way is not sending the schema, I do not know if you do that
It depends also on the use on the other clientside if it are usable ways of
course.
However maybe you can use it
Cor
> The client side is a regular VB.Net Windows Forms app. The large datasets
> brought from the Webservice to the client app usually end up in a
datagrid -
> where they may be edited and sent back (using HasChanges so getting back
> isn't an issue). From my client app I am sending back a large audit log
in
> a dataset periodically.
>
> "Cor" <(E-Mail Removed)> wrote in message
> news:eRHFOPq$(E-Mail Removed)...
> > Hi Dan,
> >
> > How are you using those datasets on the clientside.
> > I asume it is not a webservice you are talking about, but how do you use
> it
> > than?
> > Cor
> >
> > >
> > > I pass datasets back and forth between client app and web services
> (hosted
> > > on iis 5). When written to xml file these datasets can be 500kb+.
> From
> > a
> > > bandwitdth meter it seems this amount it tripled to about 1500kb for
> total
> > > traffic to send or receive these datasets thru the webservice. The
> files
> > > can be zipped down about 99% with Winzip. Should I be looking at
> zipping
> > > the dataset in code, sending the stream (via byte array) and
> > reconstituting
> > > into dataset on the receiving end? Any other preferred way to
compress
> > > this data?
> > >
> >
> >
>
>
|