In the normal course of affairs, clientDidLogon will
* be called after the client successfully logs on to the server and
* clientDidLogoff will be called after the client logs off
* of the server. If logon fails for any reson,
* clientFailedToLogon will be called to explain the failure.
*
*
clientWillLogoff will only be called when an abortable
* logoff is requested (like when the user clicks on a logoff button of
* some sort). It will not be called during non-abortable logoff requests
* (like when the browser calls stop on the applet and is about to yank
* the rug out from under us). If an observer aborts the logoff request,
* it should notify the user in some way why the request was aborted
* (but it shouldn't do so on the thread that calls
* clientWillLogoff).
*
*
If the client connection fails unexpectedly,
* clientConnectionFailed will be called to let the
* observers know that we lost our connection to the
* server. clientDidLogoff will be called immediately
* afterwards as a normal logoff procedure is effected.
*/
public interface ClientObserver extends SessionObserver
{
/**
* Called if anything fails during the logon attempt. This could be a
* network failure, authentication failure or otherwise. The exception
* provided will indicate the cause of the failure.
*/
function clientFailedToLogon (event :ClientEvent) :void;
/**
* Called when the connection to the server went away for some
* unexpected reason. This will be followed by a call to
* clientDidLogoff.
*/
function clientConnectionFailed (event :ClientEvent) :void;
/**
* Called when an abortable logoff request is made. If the observer
* calls event.preventDefault() then it will abort the logoff request.
*/
function clientWillLogoff (event :ClientEvent) :void;
}
}