Hey, ----- Original Message ----- From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
> Hi Rob,, > > On Monday 21 January 2002 14:56, Robert Koberg wrote: > > Is something that has been published content (for example, the resulting > > HTML page)? Content remains unaffected when publishing in my view. Content > > should only be affected during development and bug fixing. During QA --> > > Live the content should never change (but perhaps it's location does, or > > not). I think we are talking about semantics here, I just want to get on > > the same page. > > I was thinking about XML content that is dynamically published (as HTML or > something else), but not pre-published HTML if that is what you mean. In my > view HTML content does not exist in files, only when it is dynamically > generated (and then maybe you use wget to copy it to static files with no > more processing of any kind). > > So, for me "content" is XML stored in a repository (database or filesystem) > or generated from backend databases, and it is this content that I'd like to > be able to filter securely based on request/user/site attributes. > Do you use some kind of versioning system to retrieve a versioned-content-piece that is marked as ready for a certain stage? Or do you move versions to different locations based on the stage? Is there some Open Source java-based, versioning software that you can recommend? Is cvs the best thing for text-based version control? So the cms marks/promotes something (through the version control system) as ready for a stage and the publ sys reads which stage the request is coming from and serves the appropriate version. this makes sense now, thanks, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
