Sidnei da Silva schrieb:
I remember having a conversation with Jim at some point where he
proposed a strategy for requests that could potentially take a long
time to finish. If I recall correctly, he proposed having a separate
ZODB connection pool.
One thing that is problematic today is serving large files
from the ZODB (ignoring the upcoming blob support).
a) You can't return an iterator that reads from the ZODB, because by
the time the iterator is consumed the connection has already been
closed. I believe the iterator is not consumed in the same thread,
which can cause yet more issues.
I would like to be able to return an iterator that can read from the
ZODB. That would probably benefit the WSGI integration as well. Anyone
has ideas about how to solve this?
It should be possible to feed a fifo (at least on unix) and reopen the
connection each time via publisher or something alike (similar to the
retry mechanism on database conflicts) and fill the buffer again.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -