Hi What do you mean by "actually it doesn't"? Have you tried it? On what OS and what Zope? And thanx for the other Detail! Oliver
actually it doesn't but it is good example of some zope's optimization. so whats happening here is that ZopeFind starts looking through all the objects of the folder trying to match up requirements, when it does that it means that all these objects are now loaded from the db and are in memory/cache. after the page gets served back to the client the zpublisher thread releases its connection to the zodb, this connection's cache contains all those objects just loaded. when another request is served the zpublisher thread opens up a connection to the zodb, internal to the db these connections are stored in a FIFO stack, so the zpublisher thread ends up getting and using the connection with all those objects sitting in cache, now when the find executes it basically is operating on objects that are all in memory!
cheers
kapil