Our services use a listener to determine (actually make a best guess) at the
browser client and then loads stylesheets optimized for the browser (using
tomahawk's stylesheet control) and turns on/off functionality in the pages
and adjusts client/server updates etc.

very interesting!
I think that the listener is looking for a specific infos in the request header for guessing the browser client type, isn't it?

Also the stylesheet control allows different rendering for different clients. What isn't very clear id the client/server updates and on/off dunctionalities. I think that these actions are setted before the page is rendered; so how you can achieve it?
Maybe using a different navigation path?

Thank a lot also to the other feedbacks!

Have a nice day

Ivan

Reply via email to