Re: Transport data mixed with Application data?

[Doug Royer <Doug.Royer@xxxxxxx>]

Sure  - SENDDATA

	CUA SENDDATA
	CUS <MIME-DATA>
	CS <TRANSPORT-PROTOCOL-REPLY>
	CS <iCAL-MIME-REPLY>
	CS ...application data...
	CS <CRLF>
	CS .
	CS <CRLF>

> Date: Mon, 02 Aug 1999 13:31:59 -0700
> From: sman@netscape.com (Steve Mansour)
> X-Accept-Language: en
> To: CalSched IETF <ietf-calendar@imc.org>
> Subject: Transport data mixed with Application data?
> List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
> List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
> 
> Can anyone come up with an example of a CAP command that returns both
> transport AND application level data? I don't think we have one yet.
> 
> Several of you spoke with me after the Oslo meeting and indicated that
> the "capabilities" information we returned in the example we covered was
> really all application-level data. I tend to agree with that.
> 
> The response to a CAP command currently has this general form:
> 
>      <replycode> ; text ;  more text  <CRLF>
>      [<application-level-data>] <CRLF>.<CRLF>
> 
> If there's really a need to return transport level stuff in the same
> reply, then we'll need to change it.
> 
> Please respond if you see a problem with this.
> 
> -Steve

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL