Listeners and Server Callbacks

Client requests to the eFTL server are asynchronous. To ascertain the outcome of a request, clients must supply a callback listener.

A send call is a request that the eFTL server send a message for the client. A send call returns before the server fulfills the request. To receive information about the outcome of the send request, the application must supply a completion listener as an argument to the send call.
Note: It is good practice to supply a completion listener when using persistence features or when interacting with an EMS server.
Note: In earlier versions of the TIBCO eFTL API, send calls did not require a completion listener. It is good practice to update application programs to supply completion listeners whenever the outcome a send call is important to the application.

A subscribe call is a request that the eFTL server subscribe to messages for the client. A subscribe call returns before the server fulfills the request. To receive messages and information about the status of the subscription, the application must supply a subscription listener as an argument to the subscribe call.

A connect call is a request that the eFTL server establish a connection for the client. A connect call returns before the server fulfills the request. To receive information about the status of the connection, the application must supply a connection listener as an argument to the connect call.