Just make a live blog asset type and implement cometd from Apache and setup a streaming topic and let end viewers subscribe to the updates until the live stream is over. There will be size limits for the updates and if larger they will need to republish which could send a bit of JavaScript to tell the browser window to do so. Pass the event ID as a parameter to break the cache and tell the listener what event to pick up from. They can get the cached database version to start on initial load and then replay everything since the last refresh time. When it is all over the topic is discarded and the page moves to a static article type asset. No hard hits against the server just some little udp size packets streamed for a few minutes to a few hours as content is loaded. Numerous live blogging platforms can do this, so can you. It seems nearly all your customers want it.
Just make a live blog asset type and implement cometd from Apache and setup a streaming topic and let end viewers subscribe to the updates until the live stream is over. There will be size limits for the updates and if larger they will need to republish which could send a bit of JavaScript to tell the browser window to do so. Pass the event ID as a parameter to break the cache and tell the listener what event to pick up from. They can get the cached database version to start on initial load and then replay everything since the last refresh time. When it is all over the topic is discarded and the page moves to a static article type asset. No hard hits against the server just some little udp size packets streamed for a few minutes to a few hours as content is loaded. Numerous live blogging platforms can do this, so can you. It seems nearly all your customers want it.