How I see this happening (and other thoughts on behavior in VRML).
Fundamentally VRML objects must be able to bind to code, like java's
<app class="x">
There should be a stream field specified in VRML specifying multicast
channel or machine:port.
Objects must be able to query the browser to determine what interfaces (API's)
it supports.
Example of potential interface:
Simulation:
bind_event() //bind function to event
trigger_event() //broadcast event to
// browser if simulation is run local
// server if browser is a client
// clients if browser is a server
// to the ether if browser is peer
// on multicast channel
Interfaces should be IDL files for standards sake, and to ease
binding to OLE or CORBA compliant objects.
Potentially a protocol needs to be defined describeing the method by which
messages are broadcast and how they are addressed. DIS may take care of
this.
freeman