Media Resource Control Protocol: Difference between revisions

Revision as of 19:22, 11 April 2005

Revision as of 23:56, 24 May 2006

Line 3:

It is in the same style as [[HTTP]] and many other Internet protocols, where each message contains 3 sections: a first-line, a header and a body. The first line indicates the type of message as well as information such as response codes. The header contains a number of lines, each in the format '''<header>: <data>'''. The body, whose length is specified by the header, contains the details of the message.

Like HTTP, MRCP has requests (usually issued by the client) and responses, which may simply acknowledge receipt of the request or give other information regarding its processing. For example, an MRCP client may request to send some audio [[data]] for processing (say, for speech recognition), to which the server could respond with a suitable [[portTCP (computing)and UDP port|port]] to send the data (since MRCP does not have support for audio data specifically, this would have to be handled by some other protocol, such as [[Real-time Transport Protocol|RTP]]).

{{compu-soft-stub}}