Ticket #6131 (closed enhancement: fixed)
Addition of HTTP semantics based cometd transport: HTTP Channels
| Reported by: | kriszyp | Owned by: | kriszyp |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.2 |
| Component: | DojoX Cometd | Version: | 1.1b1 |
| Severity: | normal | Keywords: | cometd, http channels, rpc, rest, dojo.data |
| Cc: | alex |
Description (last modified by dylan) (diff)
This ticket is for the addition of a HTTP based cometd transport that utilizes the semantics of HTTP for metadata, message encapsulation, and REST information. This is mainly to provide visibility for this project that I am working on, and see if there is any feedback on it. This transport will implement the required methods for a cometd transport, and automatically plugs in as a cometd transport called "http-channels". The transport will be capable of running standalone and providing additional functionality beyond that of cometd like requesting a resource and subscribing to it at the same time. This transport can also optionally function as an enhancement to the RPC service's REST transport, to provide a means for "live" data access. Authors will be able to use the REST service, and then receive notifications of resource modifications as data changes. This will allow JsonRestStore? to provide a live view of RESTful data, resource changes will be propagated as dojo.data notification events. This addition will also involve some corrections to dojox.cometd._base to improve support for additional transports.
