split external and internal SocketIOException
---------------------------------------------
Key: CAROB-121
URL: https://forge.continuent.org/jira/browse/CAROB-121
Project: Carob
Type: Improvement
Versions: Carob 0.7.1, Carob 0.7, Carob 0.6.2, Carob 0.6, Carob 0.5
Reporter: Marc Herbert
Assigned to: Gilles Rayrat
Priority: Minor
Currently we use SocketIOException for two very different tasks:
- internally signal a network failure that we try hard to hide from the client
- externally report a programming error/a problem trying to use a closed
connection
This is dangerous because we try hard to catch "everywhere" in the code an
exception
that we... also want to throw to the user! (so NOT catching it "everywhere"
finally?!?)
For clarity these should be split into an internal SocketIOException and
external ConnectionException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
