--On 13. Oktober 2005 02:44:34 -0400 Chris Spencer
[EMAIL PROTECTED] wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing. One thread may be
ready to commit. Another may not be. If one thread calls
--On 13. Oktober 2005 02:54:51 -0400 Chris Spencer
[EMAIL PROTECTED] wrote:
But what if the client doesn't know what sources it's supposed to have?
What if it only has a limited understanding of the objects, and needs to
load certain objects on the server from scratch. Is this really a
Chris Spencer wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing.
Yes you do, each thread has its own connection to the database, and this
connection has an independent view of the database from any other thread.
Andreas Jung wrote:
Sounds like a total insane idea to me to use ZEO to distribute code :-)
Yeah, 'cos ZODB-based Script (Python)'s and ZPT's aren't code :-P
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Hi all,
this my first post to this list, and first of all thanks for your work.
I'm developing a ZODB based Collection Management software, and, for a
bunch of reasons, i have to know the list of modified objects before the
current transaction commit. Looking around seems there is no a public
--On 13. Oktober 2005 09:46:43 +0100 Chris Withers [EMAIL PROTECTED]
wrote:
Andreas Jung wrote:
Sounds like a total insane idea to me to use ZEO to distribute code :-)
Yeah, 'cos ZODB-based Script (Python)'s and ZPT's aren't code :-P
We are basically talking about the common
On 10/13/05, Chris Spencer [EMAIL PROTECTED] wrote:
I understand that, but my point was when you call transaction.commit(),
you don't necessarily know what you're committing. One thread may be
ready to commit. Another may not be. If one thread calls
transaction.abort(), they may be aborting
[Jeremy]
The default transaction manager maintains a separate
transaction for each thread. When you call
transaction.commit() from thread T1, it
commits the transaction for thread T1. It has no effect
on other thread's running transactions.
My apologies if this has been mentioned already
I'm pleased to announce the release of ZODB 3.2.10 final. This corresponds
to the ZODB in Zope 2.7.8 final. You can download a source
tarball or Windows installer from:
http://zope.org/Products/ZODB3.2
Note that there are two Windows installers, for Python 2.3 (2.3.5 is
recommended) and
Chris Spencer wrote:
I noticed that if a ZEOServer client doesn't have the definition for an
object's class, it loads it as a broken object. Is there any way to fix
the broken object by obtaining the class source from the server?
Others have commented on the status quo that your client must
Andreas Jung wrote:
...
Sorry, this is a stupid assumption.
No. It was an incorrect assumption.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com
[dvd]
this my first post to this list, and first of all thanks for your work.
I'm developing a ZODB based Collection Management software, and, for a
bunch of reasons, i have to know the list of modified objects before the
current transaction commit. Looking around seems there is no a public
Michel Pelletier wrote:
However your question of loading code from a remote location is valid,
and another Python remote object system (Pyro) that can be configured,
with some restrictions, to load code over the network:
http://pyro.sourceforge.net/
in particular, see the section on mobile
13 matches
Mail list logo
