Ok‚, set its size to
190x25px, and place it at pos
(23,42)“ or „change the text color of the label with id ‚
w47‚ to ‚
To allow for those cases, we exchanged the communication format with a simple predefined format based on JSON. With the M4 build published today, all responses from a RAP server are now plain JSON. This also makes the debugging much easier, since developer tools like Firebug display the structure of a message.
When designing the protocol, we took great care not to limit the exchange format to widgets. Instead, we created a generic synchronization protocol for any kind of objects. Objects are identified with a unique id, and every operation is related to a target object that is referenced by its unique id. There are different types of operations: one to create an object, one to destroy it, one to change some properties on an object, etc. Every message from the server contains a list of operations, besides some meta information.
You’ve guessed that we already have some prototypes for alternative RAP clients in progress. We’ll write about them soon…