samp.hub.disconnect

[Mike Fitzpatrick]

First,  I mis-read your message originally so I want to retract my
suggestion
the Mtype be 'samp.hub.event.disconnect' ;   because it is the Hub telling
the
app it is being disconnected the form should probably be
'samp.hub.disconnect'.
We probably want both forms in fact, e.g. so the hub can broadcast a
Notification to
other apps that the client was disconnected.

An argument to the message sounds reasonable.  An inactivity timeout is one
thing, if the app is being disconnected because it isn't responding then the

message may not be deliverable anyway (a good test to see that the Hub
handles this gracefully).

-Mike


On Tue, Sep 16, 2008 at 6:31 AM, Luigi Paioro <luigi at lambrate.inaf.it>wrote:

> Great!
>
> Do you think it would be worth providing the message with an optional
> argument telling the reason of the disconnection?
>
> Luigi
>
>
>  Fine with me, but I think it should be the 'event' form of the Mtype since
>> it
>> is the Hub saying it is disconnecting, and not a request to the Hub to
>> disconnect.
>>
>> -Mike
>>
>
>
>>    I would be happy to see this as a hub administrative message.
>>
>>    Mark
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ivoa.cacr.caltech.edu/pipermail/apps-samp/attachments/20080916/d5c3fc08/attachment-0001.html>