Share models across multiple clients

[GoogleCodeExporter]

Investigate the feasibility of "sharing" a Model across multiple WebGL clients 
on one page. The goal is try to reduce:
 * bandwidth usage,
 * memory usage, or
 * processing time

Once an approach is decided upon, update this issue to detail it.

Original issue reported on code.google.com by erik.kit...@gmail.com on 12 Apr 2011 at 10:41

[GoogleCodeExporter]

A way of sharing real-time data and code via NodeJS is available at:

http://nowjs.com/ 

A demo at http://nowjs.com/jazzroom allows several people to create music 
together in real-time from diifrent locations.

A very primitive version running within a WebGL context (using Three.JS as a 
framework) is described and shown at:

http://www.travisglines.com/ 

It would be cool for kuda to implement something like this.  The only issue 
would be that companies like Autodesk would have to find new things to do.  ;-)

Original comment by t.arm...@gmail.com on 14 Apr 2011 at 1:16

[GoogleCodeExporter]

Interesting! We have discussed various ideas about networking features in Kuda, 
although we shelved most discussion once websockets got the temporary boot.

This specific enhancement is to have multiple WebGL contexts on the same 
webpage for the same client share resources w/o necessarily relying on browser 
caching behavior.

Original comment by erik.kit...@gmail.com on 14 Apr 2011 at 5:18

[GoogleCodeExporter]

Pushed the change up yesterday

Original comment by khang.du...@gmail.com on 15 Apr 2011 at 5:06

• Changed state: Fixed

[GoogleCodeExporter]

Marking verified to denote this issue was part of 1.3.1 release.

Original comment by erik.kit...@gmail.com on 13 May 2011 at 5:34

• Changed state: Verified