RE: UID for IMAP Channel?

"Erev, Ari" <[email protected]> Thu, 7 Mar 2002 09:33:08 +0200
Newsgroups gmane.ietf.imap-voice
Message-ID <7D4344E32B34D511A6500002A560C60202FC0E5B@IL-TLV-MAIL4> 
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1C5AA.53B13880
Content-Type: text/plain;
	charset="iso-8859-1"

I second Alexey's suggestion to support UID with CHANNEL.

When Notification scenarios are considered, it may be that the client gets
some indication about a specific message for which it then issues a CHANNEL
command (i.e, the client did not necessarily received all sequence numbers
in the mailbox before issuing the CHANNEL command, so it can't map between
UID and sequence number). 
So, Provided that in the initial notification the UID was referenced, the
client can use UID CHANNEL directly.

Regards,
Ari Erev

-----Original Message-----
From: Lyndon Nerenberg [mailto:[email protected]]
Sent: Thursday, March 07, 2002 7:10 AM
To: [email protected]
Subject: UID for IMAP Channel?



Alexey has raised the issue of using UID with channel. I am
agnostic on this, and would like to hear from the client folks
about whether UID CHANNEL would be a useful addition to this
extension. If there is an IMAP BOF this time around perhaps
this can be discussed, and the results reported back to the
list.

--lyndon

------_=_NextPart_001_01C1C5AA.53B13880
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: UID for IMAP Channel?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I second Alexey's suggestion to support UID with =
CHANNEL.</FONT>
</P>

<P><FONT SIZE=3D2>When Notification scenarios are considered, it may be =
that the client gets some indication about a specific message for which =
it then issues a CHANNEL command (i.e, the client did not necessarily =
received all sequence numbers in the mailbox before issuing the CHANNEL =
command, so it can't map between UID and sequence number). </FONT></P>

<P><FONT SIZE=3D2>So, Provided that in the initial notification the UID =
was referenced, the client can use UID CHANNEL directly.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Ari Erev</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Lyndon Nerenberg [<A =
HREF=3D"mailto:[email protected]">mailto:[email protected]=
de.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, March 07, 2002 7:10 AM</FONT>
<BR><FONT SIZE=3D2>To: [email protected]</FONT>
<BR><FONT SIZE=3D2>Subject: UID for IMAP Channel?</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Alexey has raised the issue of using UID with =
channel. I am</FONT>
<BR><FONT SIZE=3D2>agnostic on this, and would like to hear from the =
client folks</FONT>
<BR><FONT SIZE=3D2>about whether UID CHANNEL would be a useful addition =
to this</FONT>
<BR><FONT SIZE=3D2>extension. If there is an IMAP BOF this time around =
perhaps</FONT>
<BR><FONT SIZE=3D2>this can be discussed, and the results reported back =
to the</FONT>
<BR><FONT SIZE=3D2>list.</FONT>
</P>

<P><FONT SIZE=3D2>--lyndon</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1C5AA.53B13880--