On Wed, 14 Dec 2011 19:45:07 -0500, Austin Clements wrote:
> A few minor comments below.
>
> At a higher level, I'm curious what the tag synchronization protocol
> you're building on top of this is. I can't think of one that doesn't
> have race conditions, but maybe I'm not thinking about it rig
On Wed, 14 Dec 2011 14:54:10 -0700, Mark Anderson
wrote:
> On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost
> wrote:
> > This is a time_t value, similar to the message date (TIMESTAMP). It is
> > first set
> > when the message is added to the database, and is then updated every time a
> > tag
On Wed, 14 Dec 2011 19:45:07 -0500, Austin Clements wrote:
> A few minor comments below.
>
> At a higher level, I'm curious what the tag synchronization protocol
> you're building on top of this is. I can't think of one that doesn't
> have race conditions, but maybe I'm not thinking about it rig
On Wed, 14 Dec 2011 14:54:10 -0700, Mark Anderson
wrote:
> On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost wrote:
> > This is a time_t value, similar to the message date (TIMESTAMP). It is
> > first set
> > when the message is added to the database, and is then updated every time a
> > tag
> >
A few minor comments below.
At a higher level, I'm curious what the tag synchronization protocol
you're building on top of this is. I can't think of one that doesn't
have race conditions, but maybe I'm not thinking about it right.
Quoth Thomas Jost on Dec 13 at 6:11 pm:
> This is a time_t value
A few minor comments below.
At a higher level, I'm curious what the tag synchronization protocol
you're building on top of this is. I can't think of one that doesn't
have race conditions, but maybe I'm not thinking about it right.
Quoth Thomas Jost on Dec 13 at 6:11 pm:
> This is a time_t value
On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost
wrote:
> This is a time_t value, similar to the message date (TIMESTAMP). It is first
> set
> when the message is added to the database, and is then updated every time a
> tag
> is added or removed. It can thus be used for doing incremental dumps
On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost wrote:
> This is a time_t value, similar to the message date (TIMESTAMP). It is first
> set
> when the message is added to the database, and is then updated every time a
> tag
> is added or removed. It can thus be used for doing incremental dumps o
This is a time_t value, similar to the message date (TIMESTAMP). It is first set
when the message is added to the database, and is then updated every time a tag
is added or removed. It can thus be used for doing incremental dumps of the
database or for synchronizing it between several computers.
T
This is a time_t value, similar to the message date (TIMESTAMP). It is first set
when the message is added to the database, and is then updated every time a tag
is added or removed. It can thus be used for doing incremental dumps of the
database or for synchronizing it between several computers.
T
10 matches
Mail list logo