Ewetumo Alexander

The current common approach is to hydrate the data into a serializable format (eg json) then deserialize on the client, these way a whole structure can be moved from server...

What would the current approach look like, will there be a backend DOM library to provide the similar features that the HTML Dom library requires or will a headless rendering...

I see @slimsag

When thinking about this feature, the key is to have some kind of marker for the markup being generated that allows markup generators on the client to identify their markup...

Also, Luna notified me some months back that web scrappers, mainly all major search engines, run your JS first before crawling the pages, so let this focus on code splitting...

It's possible, Just just have to be willing to disconnect your implementation from the core browser DOM On Nov 13, 2016 00:35, "Stephen Gutekanst" [email protected] wrote: > I'm marking this...

The thought was just a suggestion to see how feed stream from the db can be used as work for actors. Nothing really specific

Yes, I think this makes sense, as time as gone over, even I agree NATS is the defacto standard. Best Regards, Alex A. Ewetumo.

Through a db,a real time layered db, eg mydb by Rauch Guillermo, combines mongo and redis to create a dbstore,able to notify all clients of changes, use a db server...

Will have a crack at it