Shane Hathaway writes: Sounds like a 'rendered' export. Could you run it though the ZPublisher into a compression agent?
Chris Withers wrote:
Shane Hathaway wrote:
That's an excellent suggestion that could be taken a little further: make "static snapshot" a new option on the "export" screen. It would simply create a .tar.gz.
What's the difference between a "static snapsnot" and a normal "export" ?
Zope currently exports a big collection of Python objects, including security information, attributes, and a lot of other things. The only way to read this file is to use Zope. It is intended to make it possible to precisely reconstitute a set of objects.
A static snapshot would be a collection of HTML and graphics files, intended to be served up by a simple web server. It would not be useful to try to re-import this kind of file back into Zope; all of the metadata would be lost. Its usefulness would be the fact that, using a server such as Apache, the pages could be served at a rate of thousands of hits per second.
Shane
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Jason Spisak CIO HireTechs.com 6151 West Century Boulevard Suite 900 Los Angeles, CA 90045 P. 310.665.3444 F. 310.665.3544 Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.