> I can see the logic in this, but for me it depends on the app. If you're > talking about a CMS, then almost certainly the text will be read > from the DB > for output on the front-end *many* more times than read out for editing or > input from the back-end. Seems like a good idea performance-wise to do the > paragraphFormat() where it'll be processed least.
That depends too on the purpose of the CMS. If it's just a webCMS, then sure you might have a point. For us, we're looking at a CMS that will hold all content in a neutral form and transform for output as needed. So a web output gets HTML, while print ends up with a PDF that goes through some postscript conversion first. Even for the web though, we do mix-match storage. If the person puts html in, then they see html. If they put in ascii, they see ascii in an edit form but get some kind of html on output. I suppose it goes back to the argument about optimization. Do you "optimize" for the user maintaining the data or for the server outputting it? -Kevin ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
