Long process in zope - how a long to be ?
Hi ! I have a question about zope's python limitation. ZopeBook is say that zope's py is limited. Limited: ranges are not be to loo long, cycles (for, until) are limited, etc. I want to create two unlimited, long process. The first is an database content checker: it is check many records in an interval (1 year, 1 month, etc). So it is very slow, with many db operations. 1: The Zope is really limiting this process ? How to do it ? Terminate the thread ? 2: How to prevent the process double starting (with refresh in the browser ?) If I set a value in the session, that is good, but who delete it, when the process-or request is terminted by an exception, or zope-s termination signal ? 3: How to show the state of process ? a.) .write(), .flush(), long-long html with js tags what rewrite an readonly form input-text with actual percent ? b.) centrally stored actual result with window.setinterval(n), and periodic page reloading ? Or I walk in wrong way, I must create an outer product (a py file) with native commands, and zope only check this ? Thanx for help: ft
--On Dienstag, 28. September 2004 11:32 Uhr +0200 "kepes.krisztian" <kepes.krisztian@peto.hu> wrote:
Hi !
I have a question about zope's python limitation. ZopeBook is say that zope's py is limited. Limited: ranges are not be to loo long, cycles (for, until) are limited, etc.
Your choice is to use ZEO to keep the normal Zope client in peace and perform your own actions through another ZEO connection. -aj
Andreas Jung wrote:
--On Dienstag, 28. September 2004 11:32 Uhr +0200 "kepes.krisztian" <kepes.krisztian@peto.hu> wrote:
Hi !
I have a question about zope's python limitation. ZopeBook is say that zope's py is limited. Limited: ranges are not be to loo long, cycles (for, until) are limited, etc.
Your choice is to use ZEO to keep the normal Zope client in peace and perform your own actions through another ZEO connection.
Right. For example, once you have configured your appserver to use ZEO, you can then write your long-running stuff as filesystem scripts, and run them from zopectl. 'bin/zopectl run' leaves an object in globals called 'app', which is the root object of your ZODB. E.g.: $ cat search_objects.py # Search the ZODB, ... for obj in app.objectValues(): ...... $ bin/zopectl run search_objects.py ..... Tres. -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com
participants (3)
-
Andreas Jung -
kepes.krisztian -
Tres Seaver