[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-21 Thread Thomas Jost
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

[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-21 Thread Thomas Jost
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

Re: [PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-20 Thread Thomas Jost
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

Re: [PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-20 Thread Thomas Jost
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 > >

[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-14 Thread Austin Clements
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

Re: [PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-14 Thread Austin Clements
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

[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-14 Thread Mark Anderson
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

Re: [PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-14 Thread Mark Anderson
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

[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-13 Thread Thomas Jost
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

[PATCH 2/5] lib: Add a MTIME value to every mail document

2011-12-13 Thread Thomas Jost
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