On 01/28/2010 07:20 PM, Rajith Attapattu wrote:
For example the application may need to distinguish between the
following scenarios as the behaviour could be different for each case.
Connection closed with an error code - the behaviour would depend on
the error code.
Host unreachable - it may
On Tue, Jan 26, 2010 at 7:19 AM, Gordon Sim g...@redhat.com wrote:
On 01/25/2010 02:29 PM, Alan Conway wrote:
Should we distinguish failure to establish connection from failure of an
established connection? Note that if the client is doing failover the
distinction is somewhat blurred.
I
On 01/25/2010 02:29 PM, Alan Conway wrote:
Should we distinguish failure to establish connection from failure of an
established connection? Note that if the client is doing failover the
distinction is somewhat blurred.
I think the second point implies that if there are two separate
exceptions
On 01/21/2010 01:29 PM, Gordon Sim wrote:
The c++ and python messaging apis need to clearly define the exceptions
that can be thrown as well as when and where they can be thrown from.
As a start I'd like to compile a list of the important error conditions
that can occur. I'm hoping other will
