Hi, just a few comments on other status that may interest.
I have been testing tcp/ip networking with an implementation of the network
sensor nodes in Flux. I have been able to get the basic test examples to
work with two linux servers. An example of the nodes is given below. For the
mass avatar event at siggraph I will be working on modifying the
communications for UDP.
This raises the possibility of testing vos server with these nodes if ur
A description of the test examples and MM server is at
my experience with installing / running the server is at:
tho u would be wanting to run your own vos server.
I am also running a 2 hr multisuer virtual world BOF at siggraph (August) so
if you want me to demo vos let me know. I would want something that would
not require old browser versions, old java etc if possible because I need to
be able to demo other stuff with current tech as well.
?xml version=1.0 encoding=UTF-8?
!DOCTYPE X3D PUBLIC ISO//Web3D//DTD X3D 3.0//EN
diffuseColor='0 0 1'/
size='1 1 1'/
NetworkSensor DEF='ES' networkSensorId='ES'
field name='translation' type='SFVec3f' accessType='inputOutput'/
ROUTE fromNode='PS' fromField='translation_changed' toNode='ES'
ROUTE fromNode='ES' fromField='translation_changed' toNode='CUBE_TRANSFORM'
On 08/06/07, Peter Amstutz [EMAIL PROTECTED] wrote:
Ok, things have been a bit quiet lately, so I want to let everyone know
what's going on with VOS.
The first bit of news is that starting in July, I will be able to
dedicate half of my time (20-30 hours a week) to VOS development. I
have made an arrangement with my current employer to work part time, so
this works out well for everyone.
Second, I am continuing to do design work on s5, and have spent some
coding time doing prototyping certain crucial features to better
understand them. I've made some progress in understanding how better to
structure control flow in the presence of asynchronous requests (in s5,
*all* requests will be asynchronous) by using continuations and futures.
I'm also investigating some ideas for a new security design, which I
hope to write about to the list shortly.
Third, s5 is going to use a Python-based build system called Scons,
which I described in my email about build systems a little while ago. I
hope that this will enable a degree of automation and cross-platform
support that is impossible with autotools. I've spent some time hacking
on it and I'm comfortable with it, and it is under active development so
it seems like a safe bet.
Fourth, my intention is that come July, I will hit the ground running
with implementing s5 -- you will start seeing real progress and not just
talk. My hope is that in as little as a month or two, I can have enough
of the s5 kernel written that other people interested in helping can
Fifth, I've set up a task tracking system called XPlanner at
http://interreality.org/xplanner (login: guest, password: guest). You
can view a detailed breakdown of our development roadmap, and see both
how long we expect things to take and what progress (if any) has been
I think that about covers it. Comments?
[ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ]
[Lead Programmer][Interreality Project][Virtual Reality for the Internet]
[ VOS: Next Generation Internet Communication][ http://interreality.org ]
[ http://interreality.org/~tetron http://interreality.org/%7Etetron ][
pgpkey: pgpkeys.mit.edu 18C21DF7 ]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
-END PGP SIGNATURE-
vos-d mailing list
It be a great secret: there be more truth at the centre.
vos-d mailing list