Update of bug #27823 (project gnustep):
Status: None => Fixed
Open/Closed: Open => In Test
_______________________________________________________
Follow-up Comment #1:
I went through and checked that backends don't call the internal
connect/disconnect methods when they should be calling the public versions
(which are responsible for sending notifications).
This should be working in svn trunk now.
> Anyway, it seems rather unfriendly (and performance-hostile) to drop
> the connection just because there was an error.
I'm not sure I can agree with that ... if you are causing errors frequently
enough for dropping the connection to be a big performance issue then there's
probably something wrong with the way you are doing things.
Dropping the connection is a safety feature, to ensure that there is no
chance of a connection being left in any sort of confused state by some
unanticipated error ... but I wouldn't mind a patch to allow a connection to
attempt to recover gracefully as an option instead.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?27823>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
