Hi Leonardo, > Check your transaction boundaries. One of the reasons that most > solutions are based on an external request is that the Zope request > handler starts a transaction in the begining of the request and commits > it at the end (or rolls it back if there's an exception).
this is basically done by get_transaction().begin/commit/rollback + cleanup per executed MicroThread. We have played a lot with Zope-Transactions I think this is manageable .. Thanks for the Hint :) > Nice idea. It certainly opens a lot of possibilities (and maybe a huge > can of worms :-). Hope you can pull it off :-) Thats one of the points I could think of too .. to really make all this work, one must probably simulate different users, that "run" the processes and plug into the security-machinery .. I haven't explored this in detail yet. thank for your reply Ulrich Eck ------------------------------------------------------------------------ net-labs Systemhaus GmbH Ebersberger Str. 46 85570 Markt Schwaben fon: +49-8121-4747-11 fax: +49-8121-4747-77 email: [EMAIL PROTECTED] http://www.net-labs.de _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
