Jump to: navigation, search

Difference between revisions of "RAP/Protocol"

< RAP
(Operations)
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''NOTE: The protocol is still under development. Some details described in this document may still change until the Eclipse Juno release.'''
 
 
 
== Introduction ==
 
== Introduction ==
  
The term ''RAP Protocol'' describes the JSON-based message format used in the HTTP communication between a RAP client and a RAP server.
+
The term ''RAP Protocol'' is used to describe the JSON-based message format used in the HTTP communication between a RAP client and a RAP server.
This protocol will be introduced in RAP 1.5 to replace the plain JavaScript responses that have been used in previous releases.
+
This protocol was  introduced in RAP 1.5 to replace the plain JavaScript responses that have been used in previous releases.
After 1.5, the protocol will be extended to be used also for the HTTP requests of a RAP client.
+
As of RAP 2.0, the entire communication between client and server uses this protocol.
  
 
=== Rationale ===
 
=== Rationale ===
  
The idea of the new protocol is to fully decouple RAP server and RAP client with the intention of making the client exchangeable.
+
The idea of the RAP Protocol is to fully decouple RAP server and RAP client with the intention of making the client exchangeable.
At the point of development, the most interesting use cases have been RAP clients for mobile devices (Android and iOS), written in the client's native language.
+
At this point of development, the most interesting use cases have been RAP clients for mobile devices (Android and iOS), written in the client's native language.
 
As a consequence, all logic that is specific to the default RAP client has been moved from the server to the client.
 
As a consequence, all logic that is specific to the default RAP client has been moved from the server to the client.
 
This includes logic that relies on the existence of JavaScript or the web browser's DOM.
 
This includes logic that relies on the existence of JavaScript or the web browser's DOM.
 +
 +
A further objective for the design of the protocol was to avoid anything that would limit the protocol to the synchronization of RWT widgets.
 +
In fact, the protocol is also used for the synchronization of simple objects.
  
 
=== Advantages ===
 
=== Advantages ===
Line 27: Line 28:
 
As a consequence, messages can be parsed with every JSON parser.
 
As a consequence, messages can be parsed with every JSON parser.
 
The mime type of a response from a RAP server is <code>application/json</code> ([http://www.ietf.org/rfc/rfc4627.txt RFC 4627]).
 
The mime type of a response from a RAP server is <code>application/json</code> ([http://www.ietf.org/rfc/rfc4627.txt RFC 4627]).
 +
 +
Since JSON's grammar is already specified, we use a sloppy format to describe the protocol in the following in order to improve readability.
 +
In particular, we use the asterisk symbol <code>*</code> to indicate any number of items in an array or an object, skipping the comma that separates the items.
 +
For example, the following expression
 +
 +
<source lang="javascript">
 +
<Foo> ::= { <Key> : <Value> * }
 +
</source>
 +
 +
stands for either the empty object <code>{}</code>, an object with a single key-value pair <code>{ <Key> : <Value> }</code>, or one with multiple, comma separated key value pairs <code>{ <Key> : <Value> , <Key> : <Value> , ... }</code>.
 +
 +
We also skip the definition of the terminal symbols <code><string></code>, <code><number></code>, <code><boolean></code>, <code><any></code>, which refer to the types defined in JSON.
  
 
=== Message ===
 
=== Message ===
  
There is exactly one message in a response.
+
There is exactly one message in a request and one in a response.
 
A message contains a set of headers, followed by a list of operations.
 
A message contains a set of headers, followed by a list of operations.
 
Even if a message does not contain any headers or operations, both parts have to be present.
 
Even if a message does not contain any headers or operations, both parts have to be present.
Line 36: Line 49:
 
<source lang="javascript">
 
<source lang="javascript">
 
<Message> ::= {
 
<Message> ::= {
   "meta" : <MetaHeaders> ,
+
   "head" : <Headers> ,
 
   "operations" : <Operations>
 
   "operations" : <Operations>
 
}
 
}
 
</source>
 
</source>
  
=== Meta Headers ===
+
=== Headers ===
  
This part contains headers that describe the message itself.
+
This part contains headers that do not alter the state of the UI.
  
 
<source lang="javascript">
 
<source lang="javascript">
<MetaHeaders> ::= { <HeaderName> : <HeaderValue> * }
+
<Headers> ::= { <HeaderName> : <HeaderValue> * }
 
</source>
 
</source>
  
 
<source lang="javascript">
 
<source lang="javascript">
 
<HeaderName> ::= <string> // name of the header
 
<HeaderName> ::= <string> // name of the header
<HeaderValue> ::= <any JSON value> // value of the header
+
<HeaderValue> ::= <any> // value of the header
 
</source>
 
</source>
  
 
Example:
 
Example:
 
<source lang="javascript">
 
<source lang="javascript">
meta : {
+
head : {
 
   "requestCounter" : 23
 
   "requestCounter" : 23
 
}
 
}
Line 64: Line 77:
  
 
The operations are commands that the peer must execute in the order they appear in the message.
 
The operations are commands that the peer must execute in the order they appear in the message.
There are different types of operations: create, set, call, listen, and destroy.
+
There are different types of operations: create, set, call, listen, notify, and destroy.
 
Every operation has a target object. In case of a create operation, the target object is to be created, for all other operations, the target object must already exist.
 
Every operation has a target object. In case of a create operation, the target object is to be created, for all other operations, the target object must already exist.
  
Line 73: Line 86:
 
</source>
 
</source>
 
<source lang="javascript">
 
<source lang="javascript">
   <Operation> ::= <CreateOperation> | <SetOperation> | <CallOperation> | <ListenOperation> | <DestroyOperation>
+
   <Operation> ::= <CreateOperation> | <SetOperation> | <CallOperation> | <ListenOperation> | <DestroyOperation> | <NotifyOperation>
 
</source>
 
</source>
  
Line 80: Line 93:
 
<source lang="javascript">
 
<source lang="javascript">
 
operations : [
 
operations : [
   { "action" : "destroy", "target" : "w23" },
+
   [ "destroy", "w23" ],
   { "action" : "create", "target" : "w42", "type" : "rwt.widgets.Button", "properties" : { "visible" : false } }
+
   [ "create", "w42", "rwt.widgets.Button", { "visible" : false } ]
 
]
 
]
 
</source>
 
</source>
Line 87: Line 100:
 
==== Create ====
 
==== Create ====
  
A create operation advises the peer to create an object of the given type and associate the given id with it.
+
A create operation instructs the peer to create an object of the given type and associate the given id with it.
The CreateProperties contain properties that should be initially set on the created objects.
+
It may contain properties that should be initially set on the created objects.
  
 
<source lang="javascript">
 
<source lang="javascript">
<CreateOperation> ::= {
+
<CreateOperation> ::= [ "create", <TargetId>, <TypeName>, { <PropertyName> : <PropertyValue> * } ]
  "action" : "create",
+
  "target" : <TargetId>,
+
  "type" : <TypeName>,
+
  "properties" : { <PropertyName> : <PropertyValue> * }
+
}
+
 
</source>
 
</source>
  
Line 103: Line 111:
 
<TypeName> ::= <string> // the fully qualified name of the type
 
<TypeName> ::= <string> // the fully qualified name of the type
 
<PropertyName> ::= <string> // the name of a property to set
 
<PropertyName> ::= <string> // the name of a property to set
<PropertyValue> ::= <any JSON value> // the initial value for this property
+
<PropertyValue> ::= <any> // the initial value for this property
 
</source>
 
</source>
  
 
==== Set ====
 
==== Set ====
  
A set operation advises the peer to set a number of properties of the given target object.
+
A set operation instructs the peer to set a number of properties of the given target object.
  
 
<source lang="javascript">
 
<source lang="javascript">
<SetOperation> ::= {
+
<SetOperation> ::= [ "set", <TargetId>, { <PropertyName> : <PropertyValue> * } ]
  "action" : "set",
+
  "target" : <TargetId>,
+
  "properties" : { <PropertyName> : <PropertyValue> * }
+
}
+
 
</source>
 
</source>
  
Line 121: Line 125:
 
<TargetId> ::= <string> // the id of the object to set properties to
 
<TargetId> ::= <string> // the id of the object to set properties to
 
<PropertyName> ::= <string> // the name of a property to set
 
<PropertyName> ::= <string> // the name of a property to set
<PropertyValue> ::= <any JSON value> // the new value for this property
+
<PropertyValue> ::= <any> // the new value for this property
 
</source>
 
</source>
  
 
==== Call ====
 
==== Call ====
  
A call operation advises the peer to call a method on the target object.
+
A call operation instructs the peer to call a method on the target object.
  
 
<source lang="javascript">
 
<source lang="javascript">
<CallOperation> ::= {
+
<CallOperation> ::= [ "call", <TargetId>, <MethodName>, { <ParameterName> : <ParameterValue> * } ]
  "action" : "call",
+
  "target" : <TargetId>,
+
  "method" : <MethodName>,
+
  "properties" : { <ParameterName> : <ParameterValue> * }
+
}
+
 
</source>
 
</source>
  
Line 141: Line 140:
 
<MethodName> ::= <string> // the name of the method to call
 
<MethodName> ::= <string> // the name of the method to call
 
<ParameterName> ::= <string> // the name of a method parameter
 
<ParameterName> ::= <string> // the name of a method parameter
<ParameterValue> ::= <any JSON value> // the value for the method parameter
+
<ParameterValue> ::= <any> // the value for the method parameter
 
</source>
 
</source>
  
 
==== Listen ====
 
==== Listen ====
  
A listen operation advises the peer to listen on certain types of events.
+
A listen operation instructs the peer to issue notify operations of the given event type on the target object.
  
 
<source lang="javascript">
 
<source lang="javascript">
<ListenOperation> ::= {
+
<ListenOperation> ::= [ "listen", <TargetId>, { <EventType> : <ListenToEvent> * } ]
  "action" : "listen",
+
  "target" : <TargetId>,
+
  "properties" : { <EventName> : <ListenToEvent> * }
+
}
+
 
</source>
 
</source>
  
 
<source lang="javascript">
 
<source lang="javascript">
 
<TargetId> ::= <string> // the id of the object to set properties to
 
<TargetId> ::= <string> // the id of the object to set properties to
<EventName> ::= <string> // the name of an event
+
<EventType> ::= <string> // the name of an event type
 
<ListenToEvent> ::= <boolean> // whether to listen to the given event or not
 
<ListenToEvent> ::= <boolean> // whether to listen to the given event or not
 +
</source>
 +
 +
==== Notify ====
 +
 +
A notify operation instructs the peer to dispatch an event of the given type on the target object.
 +
Notify operations must only be issued if the peer indicated its interest in this event type using a listen operation.
 +
 +
<source lang="javascript">
 +
<NotifyOperation> ::= [ "notify", <TargetId>, <EventType>, { <PropertyName> : <PropertyValue> * } ]
 +
</source>
 +
 +
<source lang="javascript">
 +
<TargetId> ::= <string> // the id of the object to call a method on
 +
<EventType> ::= <string> // the type of the event to dispatch
 +
<PropertyName> ::= <string> // the name of the event property
 +
<PropertyValue> ::= <any> // the value for the event property
 
</source>
 
</source>
  
 
==== Destroy ====
 
==== Destroy ====
  
A destroy operation advises the peer to destroy the target object and to discard the id associated with it.
+
A destroy operation instructs the peer to destroy the target object and to discard the id associated with it.
  
 
<source lang="javascript">
 
<source lang="javascript">
<DestroyOperation> ::= {
+
<DestroyOperation> ::= [ "destroy", <TargetId> ]
  "action" : "destroy",
+
  "target" : <TargetId>
+
}
+
 
</source>
 
</source>
  
Line 177: Line 185:
 
</source>
 
</source>
  
== Data Type Reference ==
+
== Usage in RAP ==
  
In addition to the datatypes recognized by JSON itself, the RAP protocol also uses these composed types:
+
=== Common Data Types ===
  
=== Bounds ===
+
The following composed types are used for common data types in RAP:
<code> [ int left, int top, int witdh, int height ] </code>
+
  
Note that left and top may be negative. No value may be null.
+
==== Point ====
  
=== Color ===
+
<source lang="javascript">
<code> [ int red, int green, int blue, int alpha ] </code>
+
<Point> ::= [ <Left>, <Top> ]
 +
</source>
 +
<source lang="javascript">
 +
<Left> ::= <number> // integer, might be negative
 +
<Top> ::= <number> // integer, might be negative
 +
</source>
 +
 
 +
==== Rectangle ====
 +
 
 +
<source lang="javascript">
 +
<Bounds> ::= [ <Left>, <Top>, <Witdh>, <Height> ]
 +
</source>
 +
<source lang="javascript">
 +
<Left> ::= <number> // integer, might be negative
 +
<Top> ::= <number> // integer, might be negative
 +
<Witdh> ::= <number> // non-negative integer
 +
<Height> ::= <number> // non-negative integer
 +
</source>
 +
 
 +
==== Color ====
 +
 
 +
<source lang="javascript">
 +
<Color> ::= [ <Red>, <Green>, <Blue>, <Alpha> ]
 +
</source>
 +
<source lang="javascript">
 +
<Red> ::= <number> // integer between 0 and 255
 +
<Green> ::= <number> // integer between 0 and 255
 +
<Blue> ::= <number> // integer between 0 and 255
 +
<Alpha> ::= <number> // integer between 0 and 255
 +
</source>
 +
 
 +
Clients that don't support alpha values must hide the element if alpha is 0.
 +
 
 +
==== Image ====
 +
 
 +
<source lang="javascript">
 +
<Image> ::= [ <Url>, <Width>, <Height> ] | null
 +
</source>
 +
<source lang="javascript">
 +
<Url> ::= <string> // the source url to load the image from
 +
<Width> ::= <number> // positive integer defining the width of the image in px
 +
<Height> ::= <number> // positive integer defining the height of the image in px
 +
</source>
 +
 
 +
==== Gradient ====
 +
 
 +
<source lang="javascript">
 +
<Gradient> ::= [ <Colors>, <Stops>, <IsVertical> ] | null
 +
</source>
 +
<source lang="javascript">
 +
<Colors> ::= [ <Color> ] // the colors of the gradient
 +
<Stops> ::= [ <number> ] // the positions of the colors, values between 0 and 1, each equal or higher than the previous one
 +
<IsVertical> ::= <boolean> // whether the gradient is vertical
 +
</source>
 +
 
 +
The number of colors must match the number of stops.
 +
 
 +
==== Font ====
 +
 
 +
<source lang="javascript">
 +
<Font> ::= [ <Names>, <Size>, <Bold>, <Italic> ] | null
 +
</source>
 +
<source lang="javascript">
 +
<Names> ::= [ <string> ] // the names of the font families
 +
<Size> ::= <number> // the size of the font in pixel
 +
<Bold> ::= <boolean>
 +
<Italic> ::= <boolean>
 +
</source>
  
All values are to be between 0 and 255. The alpha value may be ignored by the client unless its 0.
+
The client has to use the first font-family of the names array it can display.  
  
=== Image ===
+
=== Object Type Reference ===
<code> [ String url, int width, int height ] | null </code>
+
  
=== Gradient ===
+
t.b.d.
<code> [ Color[] colors, int[] stops, boolean verticalFlag ] | null </code>
+
  
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.
+
=== Server and JavaScript-Client API ===
  
== Object Type Reference ==
+
t.b.d.
  
== Server and JavaScript-Client API ==
+
[[Category:RAP]]

Revision as of 06:27, 13 January 2013

Introduction

The term RAP Protocol is used to describe the JSON-based message format used in the HTTP communication between a RAP client and a RAP server. This protocol was introduced in RAP 1.5 to replace the plain JavaScript responses that have been used in previous releases. As of RAP 2.0, the entire communication between client and server uses this protocol.

Rationale

The idea of the RAP Protocol is to fully decouple RAP server and RAP client with the intention of making the client exchangeable. At this point of development, the most interesting use cases have been RAP clients for mobile devices (Android and iOS), written in the client's native language. As a consequence, all logic that is specific to the default RAP client has been moved from the server to the client. This includes logic that relies on the existence of JavaScript or the web browser's DOM.

A further objective for the design of the protocol was to avoid anything that would limit the protocol to the synchronization of RWT widgets. In fact, the protocol is also used for the synchronization of simple objects.

Advantages

Apart from the possiblity to connect alternative clients, the new protocol has a number of practical advantages over the previous one:

  • It produces human readable messages and eases debugging of the communication. As an example, browser extension like FireBug allow browsing the JSON messages comfortably.
  • It allows the client to create more informative error messages. With the old protocol, in case of an error, it was not clear which statement in a large message caused the error. With the new protocol, the exact operation can be identified and a strack trace can be made available.
  • It allows to add client-independent client-side scripting.

Protocol Format

The message format is a valid subset of the JavaScript Object Notation (JSON). As a consequence, messages can be parsed with every JSON parser. The mime type of a response from a RAP server is application/json (RFC 4627).

Since JSON's grammar is already specified, we use a sloppy format to describe the protocol in the following in order to improve readability. In particular, we use the asterisk symbol * to indicate any number of items in an array or an object, skipping the comma that separates the items. For example, the following expression

<Foo> ::= { <Key> : <Value> * }

stands for either the empty object {}, an object with a single key-value pair { <Key> : <Value> }, or one with multiple, comma separated key value pairs { <Key> : <Value> , <Key> : <Value> , ... }.

We also skip the definition of the terminal symbols <string>, <number>, <boolean>, <any>, which refer to the types defined in JSON.

Message

There is exactly one message in a request and one in a response. A message contains a set of headers, followed by a list of operations. Even if a message does not contain any headers or operations, both parts have to be present.

<Message> ::= {
  "head" : <Headers> ,
  "operations" : <Operations>
}

Headers

This part contains headers that do not alter the state of the UI.

<Headers> ::= { <HeaderName> : <HeaderValue> * }
<HeaderName> ::= <string> // name of the header
<HeaderValue> ::= <any> // value of the header

Example:

head : {
  "requestCounter" : 23
}

Operations

The operations are commands that the peer must execute in the order they appear in the message. There are different types of operations: create, set, call, listen, notify, and destroy. Every operation has a target object. In case of a create operation, the target object is to be created, for all other operations, the target object must already exist.

Operations must be processed in the order of their appearance in the message.

  <Operations> ::= [ <Operation> * ]
  <Operation> ::= <CreateOperation> | <SetOperation> | <CallOperation> | <ListenOperation> | <DestroyOperation> | <NotifyOperation>

Example:

operations : [
  [ "destroy", "w23" ],
  [ "create", "w42", "rwt.widgets.Button", { "visible" : false } ]
]

Create

A create operation instructs the peer to create an object of the given type and associate the given id with it. It may contain properties that should be initially set on the created objects.

<CreateOperation> ::= [ "create", <TargetId>, <TypeName>, { <PropertyName> : <PropertyValue> * } ]
<TargetId> ::= <string> // the id of the object to create
<TypeName> ::= <string> // the fully qualified name of the type
<PropertyName> ::= <string> // the name of a property to set
<PropertyValue> ::= <any> // the initial value for this property

Set

A set operation instructs the peer to set a number of properties of the given target object.

<SetOperation> ::= [ "set", <TargetId>, { <PropertyName> : <PropertyValue> * } ]
<TargetId> ::= <string> // the id of the object to set properties to
<PropertyName> ::= <string> // the name of a property to set
<PropertyValue> ::= <any> // the new value for this property

Call

A call operation instructs the peer to call a method on the target object.

<CallOperation> ::= [ "call", <TargetId>, <MethodName>, { <ParameterName> : <ParameterValue> * } ]
<TargetId> ::= <string> // the id of the object to call a method on
<MethodName> ::= <string> // the name of the method to call
<ParameterName> ::= <string> // the name of a method parameter
<ParameterValue> ::= <any> // the value for the method parameter

Listen

A listen operation instructs the peer to issue notify operations of the given event type on the target object.

<ListenOperation> ::= [ "listen", <TargetId>, { <EventType> : <ListenToEvent> * } ]
<TargetId> ::= <string> // the id of the object to set properties to
<EventType> ::= <string> // the name of an event type
<ListenToEvent> ::= <boolean> // whether to listen to the given event or not

Notify

A notify operation instructs the peer to dispatch an event of the given type on the target object. Notify operations must only be issued if the peer indicated its interest in this event type using a listen operation.

<NotifyOperation> ::= [ "notify", <TargetId>, <EventType>, { <PropertyName> : <PropertyValue> * } ]
<TargetId> ::= <string> // the id of the object to call a method on
<EventType> ::= <string> // the type of the event to dispatch
<PropertyName> ::= <string> // the name of the event property
<PropertyValue> ::= <any> // the value for the event property

Destroy

A destroy operation instructs the peer to destroy the target object and to discard the id associated with it.

<DestroyOperation> ::= [ "destroy", <TargetId> ]
<TargetId> ::= <string> // the id of the object to destroy

Usage in RAP

Common Data Types

The following composed types are used for common data types in RAP:

Point

<Point> ::= [ <Left>, <Top> ]
<Left> ::= <number> // integer, might be negative
<Top> ::= <number> // integer, might be negative

Rectangle

<Bounds> ::= [ <Left>, <Top>, <Witdh>, <Height> ]
<Left> ::= <number> // integer, might be negative
<Top> ::= <number> // integer, might be negative
<Witdh> ::= <number> // non-negative integer
<Height> ::= <number> // non-negative integer

Color

<Color> ::= [ <Red>, <Green>, <Blue>, <Alpha> ]
<Red> ::= <number> // integer between 0 and 255
<Green> ::= <number> // integer between 0 and 255
<Blue> ::= <number> // integer between 0 and 255
<Alpha> ::= <number> // integer between 0 and 255

Clients that don't support alpha values must hide the element if alpha is 0.

Image

<Image> ::= [ <Url>, <Width>, <Height> ] | null
<Url> ::= <string> // the source url to load the image from
<Width> ::= <number> // positive integer defining the width of the image in px
<Height> ::= <number> // positive integer defining the height of the image in px

Gradient

<Gradient> ::= [ <Colors>, <Stops>, <IsVertical> ] | null
<Colors> ::= [ <Color> ] // the colors of the gradient
<Stops> ::= [ <number> ] // the positions of the colors, values between 0 and 1, each equal or higher than the previous one
<IsVertical> ::= <boolean> // whether the gradient is vertical

The number of colors must match the number of stops.

Font

<Font> ::= [ <Names>, <Size>, <Bold>, <Italic> ] | null
<Names> ::= [ <string> ] // the names of the font families
<Size> ::= <number> // the size of the font in pixel
<Bold> ::= <boolean>
<Italic> ::= <boolean>

The client has to use the first font-family of the names array it can display.

Object Type Reference

t.b.d.

Server and JavaScript-Client API

t.b.d.