Jump to: navigation, search

Difference between revisions of "RAP/Protocol"

< RAP
(Introduction)
 
m (Introduction)
Line 8: Line 8:
 
* It allowes to replace either ends as long as they process and create valid RAP-protocol messages.  
 
* It allowes to replace either ends as long as they process and create valid RAP-protocol messages.  
  
The protocol is currently beeing developed in CVS HEAD. While not fully implemented, the communication will may be mixed between old and new format, e.g. JavaScript-code with embedded JSON-objects. We expect to fully switch to the new format (at least the client-to-server direction) with the 1.5 release.
+
The protocol is currently beeing developed in CVS HEAD. While not fully implemented, the communication will be mixed between old and new format, e.g. JavaScript-code with embedded JSON-objects. We expect to fully switch to the new format (at least the client-to-server direction) with the 1.5 release.
  
 
== Protocol Format ==
 
== Protocol Format ==

Revision as of 06:43, 29 August 2011

Introduction

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 is 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.

The protocol is currently beeing developed in CVS HEAD. While not fully implemented, the communication will be mixed between old and new format, e.g. JavaScript-code with embedded JSON-objects. We expect to fully switch to the new format (at least the client-to-server direction) with the 1.5 release.

Protocol Format

Data Type Reference

Object Type Reference

Server and JavaScript-Client API