Bhavin Turakhia wrote:
> - Staging - allowing to make changes and view them without publishing them
> on the website itself. i dont mean at articles and workflow level. i mean an
> entire staging copy viewable separately and allowing me to make changes for
> instance to a style an article a code-init section and see it without the
> fear that others online seeing my website rght now are also seeing it
Accomplished using a staging server and using repligard to deliver the
changes once done. Not as fine-grained as we'd want it yet.
> - Caching - pages that have already been generated should not again result
> in processing of code-init, database queries and page generation. this would
> really speeden up things.
Really hard to decide autonomously for Midgard without hints from the
site builder. The page that ends up being served to your visitor could
depend on the user, the browser, the phase of the moon... no way for
Midgard to decide whether the page needs regeneration. The site author
can, however, and emitting the correct 'Expires' tag, in combination
with a server-side cache like squid.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
