[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MODSEQ in CONDSTORE

To: Mark Crispin <mrc@xxxxxxxxxxxxxxxxxx>
Subject: Re: MODSEQ in CONDSTORE
From: Alexey Melnikov <alexey.melnikov@xxxxxxxxx>
Date: Thu, 02 Feb 2006 10:22:10 +0000
Cc: Dave Cridland <dave@xxxxxxxxxxxx>, ietf-imapext@xxxxxxx
In-reply-to: <>
List-archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-id: <ietf-imapext.imc.org>
List-unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
References: <> <> <>
Sender: owner-ietf-imapext@xxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

Mark Crispin wrote:

Clients, of course, have to deal with it as a 64-bit unsigned integer for all servers.
That's a problem. If you don't have a 64-bit integer type available in then compiler, then you have to do the work by hand. There seems to me to be no good reason for this.

Clients don't need to do any math on modsequences, they should be treated as opaque values.

And clients have an implementation option to treat modseqs as strings.

Follow-Ups:
- Re: MODSEQ in CONDSTORE
  - From: Mark Crispin

References:
- MODSEQ in CONDSTORE
  - From: Mark Crispin
- Re: MODSEQ in CONDSTORE
  - From: Dave Cridland
- Re: MODSEQ in CONDSTORE
  - From: Mark Crispin

Prev by Date: Re: MODSEQ in CONDSTORE
Next by Date: Re: MODSEQ in CONDSTORE
Previous by thread: Re: MODSEQ in CONDSTORE
Next by thread: Re: MODSEQ in CONDSTORE
Index(es):
- Date
- Thread