Issue #42 : ID manager
Initial post from issue #42.
Eric says :
Huge problem for AGATA ... Many reasons to never quit cleanly and reconnect ;(
.
bq. Lot of discussion to have.
We have at least 4 options :
- Adding some ugly patches to return always a stupid number and never check if this is accepted ....
- Adding a timeout on inactive connections, but probably some soft with nice surprise
....
- Removing cleanly ID from ENX
- Improving ID manager to authorize reconnect for example ...</cite>
Replies (3)
RE: Issue #42 : ID manager
-
Added by Legay Eric over 11 years ago
Xavier says:
Can we try to setup a "stop handler" on Ctrl^C or exit based on Ada.Finalization in order to minimize the number of unclosed connections ?
RE: Issue #42 : ID manager
-
Added by Legay Eric over 11 years ago
We cannot use "stop handler" tricks as this tricks has to be added to external software.
And in lot of case, external software is not under our control.
We have to find to manage this nicely inside ENX context I think.
RE: Issue #42 : ID manager
-
Added by Grave Xavier over 11 years ago
At least we can add it to our software as a midterm solution ?
For external software maybe if it is in Ada we can provide an API on top of the soap client API to inforce our policy ?
NB : I'm not at ease with forum(s)...