Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RAP/Protocol"
(→Protocol Format) |
(→Message) |
||
Line 19: | Line 19: | ||
=== Message === | === Message === | ||
− | There | + | There is exactly one message in a response. |
+ | A message contains of a meta part and a list of operations. | ||
<source lang="javascript"> | <source lang="javascript"> |
Revision as of 16:44, 20 January 2012
Contents
Introduction
NOTE: All information within this document is subject to change until further notice.
The RAP Protocol is the JSON-based format used within the HTTP-Requests from a RAP-client to a RAP-server. Compared with the previously used JavaScript and HTTP-fields based communication it will provide a number of advantages:
- It allowes to move all client-specific code from the server to the client.
- It produces human readable messages, easing debugging.
- It allowes the client to create more informative error messages.
- It allowes to replace either ends as long as they process and create valid RAP-protocol messages.
- It allowes to add client-independent client-side scripting.
The protocol is currently beeing developed in CVS HEAD. Server-to-Client communication is completed for all RWT-Widgets and will be part of the 1.5 release. Client-to-Server communication will possibly be implemented after 1.5.
Protocol Format
The protocol is based on the JSON fromat as described here: [ http://www.json.org/ ]
Message
There is exactly one message in a response. A message contains of a meta part and a list of operations.
{ "meta" : Meta, "operations" : [ Operation* ] }
Meta
{ "requestCounter" : <integer number> }
Operation
One of the following types:
CreateOperation | SetOperation | DestroyOperation | CallOperation | ListenOperation
Operations are processed in the order of their appearance in the message. Unkown operations will be ignored.
CreateOperation
{ "action" : "create", "target" : TargetId, "type" : TypeName, "properties" : CreateProperties }
SetOperation
{ "action" : "set", "target" : TargetId, "properties" : SetProperties }
DestroyOperation
{ "action" : "destroy", "target" : TargetId }
CallOperation
{ "action" : "call", "target" : TargetId, "method" : MethodName, "properties" : CallProperties }
ListenOperation
{ "action" : "listen", "target" : TargetId, "properties" : ListenProperties }
TargetId
The id of the target object as string
TypeName
The name of the type to create
MethodName
The name of the method to call
Data Type Reference
In addition to the datatypes recognized by JSON itself, the RAP protocol also uses these composed types:
Bounds
[ int left, int top, int witdh, int height ]
Note that left and top may be negative. No value may be null.
Color
[ int red, int green, int blue, int alpha ]
All values are to be between 0 and 255. The alpha value may be ignored by the client unless its 0.
Image
[ String url, int width, int height ] | null
Gradient
[ Color[] colors, int[] stops, boolean verticalFlag ] | null
The number of colors must match the number of stops. Each stop is a value between 0 and 1, and has to be equal or higher then the previous stop.