Warlock 2.0 #52

New issue

Closed

opened 2015-12-14 11:52:15 +00:00 by jamie · 2 comments

jamie commented

2015-12-14 11:52:15 +00:00

(Migrated from git.hazaar.io)

I've been thinking about how best to handle this and I think it's best to reverse the process. Instead of the core being message queue based for supporting long-polling and WebSockets tacked on the side, I would like the rewrite the core to work with WebSockets and have the long-polling support tacked on.

This will allow me to streamline the message processing so that messages can be ditched if nothing is subscribed to listen to the message queue.

I need to overhaul Warlock. The reasons for this are because when I originally wrote it, it was based around the concept of long-polling HTTP connections. Now that we support Websockets all of that has changed, but the core of Warlock is still the same with message queues, allowing messages to be delivered and stored for a short period until the listening host connects and subscribes (as is the case with long-polling) I've been thinking about how best to handle this and I think it's best to reverse the process. Instead of the core being message queue based for supporting long-polling and WebSockets tacked on the side, I would like the rewrite the core to work with WebSockets and have the long-polling support tacked on. This will allow me to streamline the message processing so that messages can be ditched if nothing is subscribed to listen to the message queue.

jamie commented

2016-06-27 23:31:25 +00:00

(Migrated from git.hazaar.io)

Removed ~9 label

jamie commented

2016-06-27 23:31:38 +00:00

(Migrated from git.hazaar.io)

Status changed to closed

Commenting is not possible because the repository is archived.