Thanks for your kind words. The stack is a mix of both. Browser runs on the server and sends updates to the client via websocket. Then it is painted on the client. On the client-side a part of noVNC js library is used to capture input and is sent to the browser running on the server.
Comments
Can I ask what sort of libraries you're using for the canvas-in-page-browser-selector? Is it server or client side?
The technology here is spectacular. Great job!
Thanks for your kind words. The stack is a mix of both. Browser runs on the server and sends updates to the client via websocket. Then it is painted on the client. On the client-side a part of noVNC js library is used to capture input and is sent to the browser running on the server.
Pretty slick. Could be the seed of a lightweight Browserling competitor, if you could scale it economically.
Thats an excellent suggestion. We do have plans to modularize the browser component to offer browser as a web service.