In the past I used to determine the clients screen resolution by sending out a js.
That would give me the screen resolution and I would put it into a session variable so that that client would receive the pages designed for that resolution.
Designed means, bigger/smaller fonts, bigger/smaller images, more/less colums in the product listings, etc.
The big drawback was that because it neede to be done in js, it would take at least 1 immediate redirect back to the site. Now I am only on a 800Mhz 256MB machine so any additional processing on my server part is a big issue.
It works great however with the additional advantage that you can see if the client has js enabled or not.
Still, for performance reasons I decided to make this resolution thing option/manual. That means that now everybody who enters my site does so at a 800 by 600 resolution and I have added an option to change that to 1024 by 768.
Both in the navigation bar and the footer. These settings are still stored in session variables and influence not only the loaded CSS files but also the processing of column widths, image sizes, column counts, etc.
This will save me the mandatory redirect but ofcourse will make the initial page smaller for customers who have 1024 by 768 or even higher.
Any thoughts on this from you ?
*edit* - the contribution may be downloaded here
Edited by Johnson, 18 June 2005 - 02:14 AM.