Subject: Re: [core] #227: Make aborting the previous transaction optional

From: Carsten Bormann <[email-masked]>
Date: Fri, 4 May 2012 10:48:34 +0200

> Section 4.5 requires a server implementation to stop an old transmission
> and carry the retransmit count over to the new transaction.
> 
> Cullen Jennings notes (msg03073h) that this is hard to implement in some
> cases and a minor optimization for an edge case.

(The text in question is:)
   When a server is in the process of delivering a confirmable
   notification and is waiting for an acknowledgement, and it wants to
   notify the client of a state change using a new confirmable message,
   it MUST stop retransmitting the old notification [...]

So this would be a compromise to make life easier for implementers, in exchange for worse behavior on the network.  How significant this worseness is, is dependent on your application.

This is an item that would benefit from more input from implementers.

Who has implemented this MUST?
What was your experience?
If not, would this MUST be hard to implement in your structure?

Grüße, Carsten