Hi guys. This is more of a trivia question, I guess.
Just saw something kinda strange.
Customer had a zeo server where each 4 zeo clients connected.
Some zeo clients were showing different sizes of the database.
5.2MB vs. 4.9MB.
Not that this is a big deal at all. But it was kinda strange.
It
On Jun 16, 2008, at 12:38 PM, Alan Runyan wrote:
Hi guys. This is more of a trivia question, I guess.
Just saw something kinda strange.
Customer had a zeo server where each 4 zeo clients connected.
Some zeo clients were showing different sizes of the database.
5.2MB vs. 4.9MB.
Not that this
On Mon, Jun 16, 2008 at 01:16:55PM -0400, Jim Fulton wrote:
> The client gets the size value from the storage server when it connects.
> A client gets an update of the database size when *it* commits a
> transaction. Don't ask me why it has this policy. :)
Just to make this clear for me: In my
On Jun 16, 2008, at 1:44 PM, Christian Theune wrote:
On Mon, Jun 16, 2008 at 01:16:55PM -0400, Jim Fulton wrote:
The client gets the size value from the storage server when it
connects.
A client gets an update of the database size when *it* commits a
transaction. Don't ask me why it has thi
On Mon, Jun 16, 2008 at 01:46:23PM -0400, Jim Fulton wrote:
> It isn't broadcast. It's only sent to the client that is committing a
> transaction. This is rather weird, but that's what it does.
True. I misread the code when I skimmed it earlier. Thanks.
--
Christian Theune ยท [EMAIL PROTECTED
