I haven't been active, but I wanted to jump in here.
One of the main benefits of using CSS in general is that its cached locally in the user's browser. On the first visit there is some overhead, but subsequently (if its is acting properly) the browser shouldn't request a new stylesheet if it has one of the same name in its local cache.

If I understand the thread correctly this probably isn't necessary, but I may be missing something.

-Jim

On Sep 21, 2006, at 11:43, Sean Cribbs wrote:

You make a good point about the caching.  It just might be a vulnerability to allow Radiant to edit files in the filesystem, that's all. (Remembering nightmares of PHP script-kiddies)

Sean

On 9/21/06, Tom von Schwerdtner <[EMAIL PROTECTED]> wrote:
On 9/21/06, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> What would that accomplish?  Part of the point of having it in Radiant is
> that it can be edited at a moment's notice, without worrying about file
> permissions yada yada yada.  Personally, I think it would be a slippery
> slope to allow Radiant users to edit files in the filesystem.

Perhaps he is thinking of improved performance serving the document
(eg, Squid or Apache caching)?

I don't know if it would improve anything, but thats the only
potential advantage I can think of when it comes to "TTW edit with FS
save".

-T
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to