RE: Interesting (gross?) use of CHANNEL
"Giat, Hana" <[email protected]> Sun, 10 Mar 2002 18:45:56 +0200
| Newsgroups | gmane.ietf.imap-voice |
|---|---|
| Message-ID | <7D4344E32B34D511A6500002A560C6020343FCA3@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_01C1C853.0CC78E50 Content-Type: text/plain; charset="iso-8859-1" >- Am I allowed to get the entire message instead of just a part? This seems to be reasonable: I can think about an implementation where a "thin" client on a cellular phone asks only for a message channel, and sends it to a server that will allow it fetch the data in another format. For example, an Email to Speech system. >- The document says (in a comment) > You cannot ask for .HEADERS or .MIME data with CHANNEL. >Why not? I think that CHANNEL is mainly a shortcut to the data. This is not reasonable to ask for a 250 bytes shortcut to a 200 bytes response. That's why. Hana Giat Comverse -----Original Message----- From: Pete Resnick [mailto:[email protected]] Sent: Saturday, March 09, 2002 8:45 PM To: Lyndon Nerenberg Cc: [email protected] Subject: Re: Interesting (gross?) use of CHANNEL OK, so now I have a couple of questions: - Am I allowed to get the entire message instead of just a part? - The document says (in a comment) You cannot ask for .HEADERS or .MIME data with CHANNEL. Why not? -- Pete Resnick <mailto:[email protected]> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 ------_=_NextPart_001_01C1C853.0CC78E50 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: Interesting (gross?) use of CHANNEL</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>>- Am I allowed to get the entire message instead = of just a part?</FONT> <BR><FONT SIZE=3D2>This seems to be reasonable: I can think about an = implementation where a "thin" client on a cellular phone asks = only for a message channel, and sends it to a server that will allow it = fetch the data in another format. For example, an Email to Speech = system.</FONT></P> <P><FONT SIZE=3D2> </FONT> <BR><FONT SIZE=3D2>>- The document says (in a comment)</FONT> </P> <P><FONT SIZE=3D2>> = You cannot ask for .HEADERS or .MIME data with CHANNEL.</FONT> </P> <P><FONT SIZE=3D2>>Why not?</FONT> <BR><FONT SIZE=3D2>I think that CHANNEL is mainly a shortcut to the = data. This is not reasonable to ask for a 250 bytes shortcut to a 200 = bytes response. That's why.</FONT></P> <P><FONT SIZE=3D2>Hana Giat</FONT> <BR><FONT SIZE=3D2>Comverse </FONT> </P> <P><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: Pete Resnick [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>]<= /FONT> <BR><FONT SIZE=3D2>Sent: Saturday, March 09, 2002 8:45 PM</FONT> <BR><FONT SIZE=3D2>To: Lyndon Nerenberg</FONT> <BR><FONT SIZE=3D2>Cc: [email protected]</FONT> <BR><FONT SIZE=3D2>Subject: Re: Interesting (gross?) use of = CHANNEL</FONT> </P> <BR> <BR> <P><FONT SIZE=3D2>OK, so now I have a couple of questions:</FONT> </P> <P><FONT SIZE=3D2>- Am I allowed to get the entire message instead of = just a part?</FONT> </P> <P><FONT SIZE=3D2>- The document says (in a comment)</FONT> </P> <P><FONT SIZE=3D2> You = cannot ask for .HEADERS or .MIME data with CHANNEL.</FONT> </P> <P><FONT SIZE=3D2>Why not?</FONT> <BR><FONT SIZE=3D2>-- </FONT> <BR><FONT SIZE=3D2>Pete Resnick <<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>&g= t;</FONT> <BR><FONT SIZE=3D2>QUALCOMM Incorporated - Direct phone: (858)651-4478, = Fax: (858)651-1102</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C1C853.0CC78E50--