[Zope-ZEO] Re: ZEO 0.2.1 - still not right on NT?
Jim Fulton
jim@digicool.com
Mon, 10 Jul 2000 09:12:05 -0400
Jim Fulton wrote:
>
> Jeffrey Kunce wrote:
> >
> > I gave ZEO 0.2.1 a try on NT. Changes on one client are still not immediately apparent on another client. If you stop a client, and start again, the changes from the other client are visible.
> >
> > However, while running back and forth between machines, making changes one one, checking the other - at one point I made a change and did a commit and got this traceback:
> > >>> get_transaction().commit()
> > Traceback (innermost last):
> > File "<stdin>", line 1, in ?
> > File "F:\software\Zope22b3\lib\python\ZODB\Transaction.py", line 251, in commit
> > File "F:\software\Zope22b3\lib\python\ZODB\Connection.py", line 266, in commit
> > ZODB.POSException.ConflictError:
> >
> > And then I could see changes that had been made on the other client!
> >
> > So it's closer than 0.2 - once ConflictError is hit, the two clients seem to be synchronized.
> >
> > I have a couple of other ZEO/NT notes that I'll post in a separate message
>
> I haven't seen this and can't reproduce it. I'll be interested to hear
> what reports other folks have.
Hm, I didn't try running the server on NT. I wonder if that has anything to do with it.
Jim
--
Jim Fulton mailto:jim@digicool.com Python Powered!
Technical Director (888) 344-4332 http://www.python.org
Digital Creations http://www.digicool.com http://www.zope.org
Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission. Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.