Re: [xmlblaster-devel] how to diagnose subscriber that stops getting messages after a while?

[Marcel Ruff <mr at marcelruff.info>]

Salute,

Brad Clements wrote:
> On 14 Jul 2006 at 12:19, Marcel Ruff wrote:
>
>   
> > See 
> > http://www.xmlblaster.org/xmlBlaster/doc/requirements/interface.update
> > .html#exception
> >
> > I think you should catch everything and do whatever is appropriate for
> > your clients use case. 
> >     
>
> My question was about Python client library and what it should do.
>   
See the link above
"If clients written in other programming languages send a weird 
exception error code, it is handled by the server as 
"user.update.internalError" (for Corba access since ever, for SOCKET and 
XMLRPC since xmlBlaster 1.3, before it was a "internal.unknown" or 
"internal.illegalargument")."


> The url you gave above describes what the Java client library does, thanks.
>
> However what that page says is not really complete.
>
> It says that if some other exception type is thrown by the client application, the 
> java client library convers them to "user.update.internalError" but that paragraph 
> doesn't describe what xmlblaster does with such exceptions. 
>   
See the link above
"The current error handler is implemented to publish this message as a 
'dead letter', that is a message with the |key oid='__sys__deadMessage'|."
Only |"user.update.holdback"|  has the special meaning as described.

regards,
Marcel
>   

> Do they go to dead letter, or to "holdback"?
>
>
>