[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: identity persistence and comparison issues
On 24-jun-04, at 1:28, Erik Nordmark wrote:
One could argue that the application should inform the "stack" about
the lifetime of the communication, perhaps by defining some new "open"
and "close" APIs, i.e. getting close to defining a session layer.
But my gut feel is that this requires more changes to the applications
than is warranted.
Hm, I think you're overlooking the fact that in any case where
referrals happen, the host that's being referred to must accept
incoming connections. An application waiting for incoming connections
is something that's pretty easy to detect for a host stack...
In other words, the bind(2) call can trigger the creation of a
longer-lived identifier. Still, I'm not sure how applications determine
which address to use in referrals, it may be necessary to make this an
explicit API call = application changes = a bad thing.