[Catalog-sig] start on static generation, and caching - apache config.

Jim Fulton jim at zope.com
Mon Jul 9 15:49:32 CEST 2007

What Martin said :), and:

On Jul 7, 2007, at 11:14 PM, René Dudfield wrote:
> Logged in users will not see the static file anyway - since they are
> logged in, they get to see the dynamically generated stuff.

Here's a common use case:

- A user uploads a new release

- They then use setuptools to install the release from PyPI.   
setuptools will not present their credentials and will therefore  
behave like a logged in user.  It will see and install an older  
version of the package.

This will be very mysterious and annoying to the user that just  
uploaded the release.

> Imagine this case:
> 2-3 users are updating their packages, at a similar time.  The main
> index then gets regenerated 3 times, rather than once.

Who cares.  That's one page that we get dynamically now.

>   The more
> people who are changing things the more this method works.  If there
> are 20 people changing things at the same time, then there is still
> only one update of the main index page.  However since the cheeseshop
> only gets updated about 6 times daily, event based is probably better
> for the moment.


> Anyway... I'm just making the tool which can be used on demand, or at
> regular timings.

I wonder if we are talking about the same thing here.  I fear not.   
With event based update, you should only update the pages that need  
to be updated, at worst, this should be the pages for the project  
being updated plus http://www.python.org/pypi/.  The software needed  
for this would be very different than the software that would build  
the static pages initially or update all if a template has changed.


Jim Fulton			mailto:jim at zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org

More information about the Catalog-SIG mailing list