Issue 415: Connections are not reclaimed properly
http://code.google.com/p/mobicents/issues/detail?id=415
Comment #3 by baranowb:
OK this doesnt make a sense to me.
1. there is no method to reinstantiate connection.
2. close/failed connection is not a valid source of information isnt it?
3. lingering connection makes app depend on implementation - for instance
PR, or AN
endpoints have limit, app would have to retry and watch for error message?
THey
listen to connection close state which != removed from endpoint, which is
bad.
-Endpoint allocates resources for connection (not a connection for itself).
-Endpoint and ONLY Endpoint can create or delete connections upon Call
controller
I agree, but sequence of actions is not correct, what seems correct to me
is:
1. connection is create - state OPEN or any lower
2. connection fails/is closed
3. connection stops
4. connection disposes of any allocated resources
5. notifies endpoint that its state has shifted to closed
6. endpoint clears resources
7. endpoint removes connection
Possibly #6 should be shifted.
Otherwise CLOSED is meanigless for listeners as it only dissalows to modify
connection in MMS.
Lets make decision wheather this is valid or not
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
