[Neil Piercy <Neil.Piercy@xxxxxxxxxxxx>]

Guy Harris wrote:

> You could define and implement a notion of a "conversation" different from
> the transport-layer end-point oriented notion implemented by the current
> conversation code, and use that instead.

I've come across a couple of occasions where it would have been nice to 
include an arbitrary (say 32 bit) "sub-conversation" id to distinguish 
between multiple conversations between the same transport endpoints. The 
use I had in mind was for protocols which provide multiple endpoints to 
their higher layers whilst using a single transport endpoint below, and 
you wish to track the conversations within those higher layer endpoints.

I've not got round to doing anything about it (yet), but would this be a 
good thing to add to the existing conversations, or add a new API along 
side the existing ones ?

Neil