Subject: Re: [speechsc] Content-Length: 0

From: "Dave Burke" <[email-masked]>
Date: Sat, 13 May 2006 13:26:52 +0100

Ahem - we have CRLF so down-grade this to minor ;-) However, note that SIP mandates Content-Length for stream protocols so MRCP is somewhere in between HTTP and SIP as far as its Content-Length requirements are...

Dave
  ----- Original Message ----- 
  From: Dave Burke 
  To: [email-masked] 
  Sent: Saturday, May 13, 2006 1:22 PM
  Subject: [speechsc] Content-Length: 0

  For all the discussions about protocol parsing efficiency, I think we could be missing something more serious. Currently, for Content-Length, we say

     ...it MUST be included in all messages that carry content beyond
     the header portion of the message...

  MRCP runs over stream-oriented protocols so how do you delimit the end of the message if their is no body? Right now, it would appear you need to wait for the next one to appear! The obvious fix is to change the spec so that Content-Length must appear on all messages, i.e. including those without a message body. Thus Content-Length: 0 delimits the end of a message.

  Dave

_______________________________________________
Speechsc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/speechsc