At 10:21 PM +0100 1/15/16, Tom Frost wrote:
Wouldn't dispatching commands coming in from http over chat and
MessageLinked make things slow again?
MessageLinked and chat are fast enough. We are not targeting 200
events/sec. ~20/30 are enough for smooth control, that is no
perceivable discontinuity.
I must say, i've never considered using incoming http requests.
Once upon a time, we had mail. Then we had XML-RPC. Finally, HTTP in.
In my opinion, HTTP is the most flexible of all when you want to
shuttle data in and out. The main pain is to track URL's (they change
each time the sim restarts). You need to register to a database via a
web service, and resolve names to changing URL's. Thus, an object can
call the resolver, get the URL of another object (possibly on another
grid) and initiate a direct communication.
Fun story : when I was scripting on a public grid, my objects were
inadvertently included in oar's then replicated onto other grids.
Suddenly, I was receiving registration requests from unknown grids.
Since that, I have included a remote kill feature.
The in-world scripts I made that need interaction outside of the sim are
low-frequency and generally pull-based.
I'm a real-time guy, so I was interested from the beginning to push
the limits. Years ago, I was using UDP and C# scripts to communicate.
I'm doing all over HTTP now.
Curious to see though, where you're endeavours are going to lead :)
This is opensimulator, so we are probably going to simulate
something. Maybe a factory, a nuclear plant, an industrial process, a
physics experiment... We want things that work when we act on them.
And we want nice control panels, dont' we? The time of prim buttons
and xyText is over. Design in HTML and cast it inside opensim.
-- Jeff
_______________________________________________
Opensim-users mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
