This page describes Client application instance management on the server:

Flex

- When the Flex application connects first time to the back end it will query the server to assign a client identifier (it does not matter if the call is made using an AMF or RTMP channel).

- FluorineFx will assign a client identity and will create the corresponding Client object (accessible through FluorineContext.Current.Client)

• If the connection was made over an AMF channel the Client object is created with a sliding expiration of 1 minutes.
• If the connection was made over an AMF channel with polling the Client object is created with a sliding expiration of 1 minutes or longer depending on the polling interval.
• If the connection was made over an RTMP channel the Client object never expires (as it is bound to the persistent RTMP connection)
• Any subsequent call over an RTMP channel will remove the sliding expiration of the Client object (if it was created by an AMF-RPC call)
• Additionally the sliding expiration of the Client object can be controlled by the /services-config/flex-client section (overwrites the above if it is set to greater then 0)

- For any subsequent call the Flex application will send the client identifier (global FlexClient Id)

- FluorineFx will restore the FluorineContext.Current.Client using the received identity. If the Client object has already expired the back end will create a new instance.

Flash RTM applications

The Client object is available only for RTMP applications. There is no sliding expiration set unless the /services-config/flex-client section specifies otherwise.