Ticket #556 (closed Enhancement: fixed)
The Webclient should process Directives returned by a plugin's resource method
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.1.3 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.1.2 |
| Keywords: | Cc: | dgf, Malte | |
| Complexity: | 3 | Area: | Application Framework / API |
| Module: | deepamehta-webclient |
Description (last modified by jri) (diff)
Currently the Webclient processes only the directives returned by the Core service. It should process directives returned by a Plugin service as well.
Note: processing directives should remain the responsibility of the Webclient. The plugin developer is not supposed to care about.
Goal is sort of "data binding": automatically sync the Webclient's (topicmap) view when something changes at the server.
(Note: directives are still send as response to a request. Server push is not addressed here.)
Thank you, dgf, for bringing up this issue!
Change History
comment:3 Changed 11 years ago by Jörg Richter
Webclient: process directives from plugins (#556).
The Webclient (actually the RESTClient) automatically processes directives sent by a plugin service.
So a plugin resource method can return directives now. They are processed at client-side automatically.
Existing plugins require no changes.
CHANGES
3rd-party DM webclients:
The RESTClient constructor method has changed. It takes one optional config object now as the argument.
For the moment the config object expects one (optional) property:
process_directives -- a function that processes the directives returned by the server.
The former core_service_uri RESTClient constructor paramter is gone. As the core service uri /core is now hardcoded.
See #556.
