[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (#2) Byte reduction in BEEP commands.
Patrice Lapierre wrote:
> There are many ways a command can be aborted:
> (1) CUA sends an "abort" message at any moment from
> another channel.
> (2) CUA sends an "abort" RPY to a "timeout" MSG
> (when max lantency is exhausted).
> (3) Max latency is reached and action='abort'
> For (2), I agree.
> For (3), cmdid is not an issue, but your text seems correct
> since we can say that it's not the CUA that aborts the
> For (1), I think that the cmdid must always be present,
> even if only a single command is present. The motivation
> is that there might be delay before the CS processes the
> "abort" command. Without the "cmdid" the server will not
> be able to unambiguously determine which command to cancel
> (even if there is only one it could have been sent after
> the "abort").
In (1) the CUA is doing more than one command at a time.
So yes when the CUA sends more than one command at a time
and it may wish to cancel the command, it MUST supply CMDID.
But if the CUA is NEVER going to send more than one command
and is not using latency, then it NEVER is needed.
org:INET-Consulting LLC <http://INET-Consulting.com
title:Chief Executive Manager