>Client Side Programs:
>
>Any time you put anything on the client machine it has an increased
>chance to disturb the delicate operations within. A client side
>program is more trouble then it is worth and for each person I have to
>help configure a client is a chunk out of my day. In addition, there
>isn't one single program out there that you can use on Windows 95,
>WindowsXP, Windows 2000, Macintosh 7, 8, 9, X, and Linux which means I
>have to maintain setup instructions for each distribution not to
>mention different client packages have different features.
Excactly
>I rather keep everything server side, force everyone to use a
>mozilla/Netscape browser (available on all platforms) and maintain one
>set of instructions on how to set up ziproxy. See...wasn't that
>easier? :)
Not so easily done in the wild. Our application of Ziproxy will only
have to work with Windows and IE 5 or later fortunately. We are
trying to find a way to configure the proxy without any user input.
We haven't quite done that yet though.
You latest comments (which I deleted) are starting to make it a lot
more complicated and I can see where you would end up with some
things getting compressed that you don't want and some not that you
do. It might make more sense to go back to your original request and
just hava switch to turn off compression of gif images. As you said
they are usually small. If they aren't then they have more
information that you might want to see.
I am curious about your comments on the PNG images crashing Macs. Is
that a browser problem or a Mac problem? PNG images have significant
advantages over GIFs.
--
Knute Johnson
Molon Labe...
|
