Kripken wrote: > be just a subset of MXP, without e.g. the position/movement updates > and so forth. And my main point is that a *fixed* protocol using > Google Protocol Buffers etc. on top of MXP, isn't enough; the protocol > needs to be able to change in each area you connect to.
I thought that exactly is the idea: use google protobufs for your own stuff, application specific custom network packets. Like we've done with e.g. raknet when making games. > Of course, the API/DOM must allow stuff like you mentioned above, > including input handling, entity/object control, visual effects, > sound, etc. etc. That stuff is an area where I do not think much > innovation is needed, it is fairly straightforward. Agreed. Just something we need to do in a sane enough way in Naali too. Am looking forward to seeing more how it is in other places. > My argument here has been that such an API/DOM needs to also allow > each region to have its own custom network protocol. I don't see any > other way that would allow a single client to connect to different > kinds of worlds, SL/Quake/ etc. So that is what Syntensity uses, and I > don't think we have found any fundamental problems with the approach > so far. I think that is the way too. Games usually work by having own packets for the things that happen in that game / world. > Btw, to repeat myself from the past, I would be very happy to work > with realXtend on this. The less duplicated effort the better. Right-o. Like said I think we must study Syntesity more at this end once get the chance. Is also always interesting to hear more about what you'd expect from us. > - kripken ~Toni --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/realxtend http://www.realxtend.org -~----------~----~----~----~------~----~------~--~---
