Hi Roall
Thanks for your comments, they have lead to more thoughts..., apologies to
my ignorance in advance.
> > ..unsure how this will impact the performance
> >
>
>Yes and its here you will get opinions which claim that your idea is bad.
>But there are no bad ideas ,only ideas that leads to other/better ideas
>
>If your site have a lot of users it will become slow if you are
>transforming
>every article every time. Users should not tolerate slow sites if its not a
>econimical question, but thats not the case here.
>
>But the article writers...
>The next idea is to do the transformation once
>(or twice if the content or design is changed).
>
>In clear text: Transform when content is published or republished.
Yes, I agree fully with you on this. This is an area which gets unclear for
me. My belief is that the 'transform or not to transform' responsibility
should go with the transformation service/software. By this I mean that I
should not be writing code to check if an article is updated or not - I can
of course do this if needed and hide it from my client servlets [e.g. serve
from cache or pick up the output from a file containing the output of a
transform, of course I'll still need to check for article changes].
I'm very unsure on how to proceed in this area because XSLT is offered by
Turbine, Cocoon and Jetspeed [which is of course powered by Turbine, Cocoon
and other stuff]. I like what Jetspeed offers [I can design my entire site
viewing everything as portlets which seems extremely flexible] but I've been
advised that it's too early days to use it in anger! I'm not even sure if
the XSLT Service in Turbine is utilising Cocoon in some way [I'm still
trying to educate myself on all these products] or if it's completely
separate!
All/any comments very much appreciated...
Regards, Hong
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
