Opened 14 years ago

Closed 14 years ago

Last modified 12 years ago

#6131 closed enhancement (fixed)

Addition of HTTP semantics based cometd transport: HTTP Channels

Reported by: kriszyp Owned by: Kris Zyp
Priority: high Milestone: 1.2
Component: DojoX Cometd Version: 1.1b1
Keywords: cometd, http channels, rpc, rest, Cc: alex
Blocked By: Blocking:

Description (last modified by dylan)

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 notification events. This addition will also involve some corrections to dojox.cometd._base to improve support for additional transports.

Attachments (1)

channels.diff (18.3 KB) - added by kriszyp 14 years ago.
HTTP Channels

Download all attachments as: .zip

Change History (9)

comment:1 Changed 14 years ago by Jared Jurkiewicz

Who is implementing this? Who should it be assigned to?

comment:2 Changed 14 years ago by kriszyp

I am implementing it, I just filed the ticket so it would have a ticket and I could see if there are any concerns/issues related to it. This is cometd (so maybe Alex), but it will have an effect on RPC (maybe Dustin) and some of the stores, so I am not sure who it should be assigned to.

comment:3 Changed 14 years ago by kriszyp

Or obviously it could be assigned to me, just wasn't sure if you wanted it assigned to a committer.

comment:4 Changed 14 years ago by Jared Jurkiewicz

Owner: changed from Jared Jurkiewicz to kriszyp

I'll just assign it over to you, since you're doing it.

Changed 14 years ago by kriszyp

Attachment: channels.diff added

HTTP Channels

comment:5 Changed 14 years ago by dylan

Cc: alex added
Description: modified (diff)

Kris, I've noticed some code blocks commented out in a few places. Should those be removed?

Alex, can we get a code review on this patch please?

comment:6 Changed 14 years ago by alex

Component: DojoX DataDojoX Cometd

comment:7 Changed 14 years ago by Kris Zyp

Resolution: fixed
Status: newclosed

(In [14136]) fixes #6131

comment:8 Changed 12 years ago by bill

Owner: changed from kriszyp to Kris Zyp
Note: See TracTickets for help on using tickets.