Jump to: navigation, search

Difference between revisions of "RAP/Server Push"

< RAP
(Requests)
Line 2: Line 2:
 
It's based on the so-called [http://en.wikipedia.org/wiki/Comet_(programming) Comet] approach, i.e. it uses a long-standing request that is answered only in case of server-side updates.
 
It's based on the so-called [http://en.wikipedia.org/wiki/Comet_(programming) Comet] approach, i.e. it uses a long-standing request that is answered only in case of server-side updates.
  
=== Requests ===
+
=== Request Types ===
 
There are two different types of requests involved:
 
There are two different types of requests involved:
  
==== UI requests ====
+
* UI requests: normal Ajax requests that synchronize client and server.
  
Normal Ajax requests that synchronize client and server.
+
* Callback requests: long-standing Ajax requests for server notifications to the client.
 
+
==== Callback requests ====
+
 
+
Long-standing Ajax requests for server notifications to the client.
+
  
 
=== Activation ===
 
=== Activation ===

Revision as of 10:17, 19 July 2011

The UICallback is RAP's mechanism to push UI-changes to the client. It's based on the so-called Comet approach, i.e. it uses a long-standing request that is answered only in case of server-side updates.

Request Types

There are two different types of requests involved:

  • UI requests: normal Ajax requests that synchronize client and server.
  • Callback requests: long-standing Ajax requests for server notifications to the client.

Activation

The UICallback mechanism is activated and deactivated on the server. When the activation state changes, the property uiCallbackActive is updated on the client.

When the property uiCallbackActive is true, the client ensures that there is an active connection to the server.

Callback requests

After processing the response to a ui request, the client sends a new callback request if the uiCallbackActive property is true and there is no current callback request standing.

When a callback request fails, the client sends a new callback request to re-establish the broken callback connection. To avoid unnecessary load on the client, retry requests are sent with a suitable delay.

In the response to a callback request, the server can advise the client to send a ui request if needed. Because every ui request must synchronize client and server, this ui request must contain any pending changes on the client. This request does not differ from requests that are sent as a result of a user interaction.

API Calls that affect the UI Callback

The following actions cause a standing callback request to be responded to.

UICallBack#activate() / deactivate()

UICallBack#activate() enables the UICallBack system. This method must be called inside of a ui request.

UICallBack#deactivate() causes a standing callback request to return if no other instance requires the UICallBack system.

When the activation status changes, the next returning request (either a ui or a callback request) will update the uiCallBackActive property.

Display#(a)syncExec()

The runnable that is passed to (a)syncExec() is put in a queue and executed in the next call to Display#readAndDispatch().

If Display#(a)syncExec() is called outside of a ui request, it causes a standing callback request to return and trigger a new ui request. If a ui request is currently running, the (a)sync runnable is being processed by this ui request. In this case, the callback request is not released.

Display#wake()

If Display#wake() is called outside of a ui request, it causes a standing callback request to return and trigger a new ui request. If this method is called while a ui request is processed, it does nothing.