Using ASP.NET 2.0.
The HTTP compression that comes with IIS 6.0 is great for compression
downstream.
However, there doesn't seem to be any standard way of compressing upstream
(eg. on postback, to reduce size of ViewState etc).
Does anyone use any compression solutions for reducing the amount of network
traffic going upstream ?
On Apr 8, 7:33=A0am, "Moe Sisko"
> Using ASP.NET 2.0.
>
> The HTTP compression that comes with IIS 6.0 is great for compression
> downstream.
> However, there doesn't seem to be any standard way of compressing upstream=
> (eg. on postback, to reduce size of ViewState etc).
>
> Does anyone use any compression solutions for reducing the amount of netwo=
rk
> traffic going upstream ?
You may find solutions that involve the installation of software on
both the server-side and client-side, but that doesn't solve the
problem when dealing with Internet users.
Most web applications are optimized by reducing the amount of data
transferred - such as by disabling the viewstate for unnecessary
controls. Besides, HTTP compression isn't supported by all devices/
browsers so in some cases, it's the only way to go.
Lets clear the definitions first....
Am I correct in my assumption that
Upstream - goes from browser to server...
Downstream - goes from server to browser...
Obviously you have little or no control over browser and the way it send
information...
You can though have your own serialization for ViewState thus compressing it
on a fly. Thus reducing the amount of data that goes Upstream..
George.
"Moe Sisko"
news:uZlfIlSmIHA.3780@TK2MSFTNGP06.phx.gbl...
> Using ASP.NET 2.0.
>
> The HTTP compression that comes with IIS 6.0 is great for compression
> downstream.
> However, there doesn't seem to be any standard way of compressing upstream
> (eg. on postback, to reduce size of ViewState etc).
>
> Does anyone use any compression solutions for reducing the amount of
> network traffic going upstream ?
>
>
>