Difference between revisions of "RAP/Protocol"

Revision as of 10:57, 15 December 2011

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

 
{
  "meta" : MetaObject,
  "operations" : [ (OperationObject)* ]
}

There has to be exactly one message per request and one per response. (May differ while in development.)

MetaObject

{ 
  "requestCounter" : int
}

OperationObject

TODO

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

Width and height are mandatory. If there is no image the entire value has to be null.

Object Type Reference

Server and JavaScript-Client API