cliffhall

This example renders thirty frames of the Three.js 'your first scene' example and sends them to a Node.js microservice, which saves them to the filesystem.

test-render-client.html

• Creates the scene, camera, renderer, and kicks off the render loop, which stops after 30 frames have been rendered.
• As an optimization, it doesn't add the Three.js canvas to the browser DOM, rendering it offscreen, but reporting progress.
• It extracts the data for each frame using canvas.toDataURL(), sending that to a web worker process for transmission.
• When all frames are rendered, it sends a 'done' message to the worker.

test-render-worker.js

• Sets up a queue for incoming frames to be sent to the server.

cliffhall

The client is a refactoring of the Websocket test found at: http://websocket.org/echo.html The server is a simple Node.js Socket.io server which responds to the client's 'test' event, by responding with the client connection id. When the client receives the server's 'test' event, it closes the connection.

See http://cliffordhall.com/2016/10/persistent-connections-with-socket-io/