Ticket #557 (closed Enhancement: fixed)
Remove Webclient dependency from DM's RESTClient
| 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
Removing the dependency would better support embedding of the DM RESTClient in 3rd-party DM clients.
The dependency was introduced in DM 4.1.1 in conjunction with the client-side "pre_send_request" hook.
Thanks, Malte, for bringing up this issue!
Change History
comment:2 Changed 11 years ago by Jörg Richter
- Status changed from accepted to closed
- Resolution set to fixed
RESTClient: remove Webclient dependency (#557).
The RESTClient no longer depends on the Webclient.
This makes it more easy do deploy the RESTClient in 3rd-party DM Webclients (like Malte's Twitter-Citymap).
CHANGES
The config argument passed to the RESTClient constructor takes another property:
on_send_request -- Optional: the callback invoked before a request is sent (a function). One argument is passed: the request, an object with these properties: method, uri, header, and data.
Close #557.
