Ah ha! but you are forgetting that JSP can also include (statically) or (dynamically)
content
You can <jsp:include> a personalisation stylesheet.
You can also have more than one stylesheet two.
<%@ page include file="personalisation.css" %>
<LINK REL="stylesheet"
TYPE="text/css" HREF='site.css'>
You dont have to wrote about the issue then
Also rather than storing the style definitions in the database it might be better
to store just the "class" name themselves associated with each HTML Element
and then define the style as normal in the CSS internal or external
--
Peter Pilgrim | | ++44 (0)207-545-9923
.... \ \ ___ / / ... .
- ---- ( * ) --- --
_____________________________Cafe_Savannah,_San Antonio,Ibiza__
---------------------------------------- Message History
----------------------------------------
From: "Max Cooper" <[EMAIL PROTECTED]> on 07/09/2001 05:19 MST
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: Personalisation Best Practice
Watch out for browser caching issues with a JSP stylesheet. It may be slow
to adopt new preferences because the browser is using a cached copy. Turning
caching off might hurt the performance of both the server (having to
regenerate the stylesheet for each page view) and browser (having to
download the stylesheet for each page view).
--<CUT>--
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
