[X3D-Public] XMPP or not XMPP

Tony Parisi tparisi at gmail.com
Wed Sep 1 10:21:50 PDT 2010


I think for floating data you could just use text over XMPP. We're not
talking about a lot of data: positions and orientations mostly.

Zlib is an interesting idea - not sure either but that would be great to

I would NOT repeat NOT transfer large hunks of data over the MU protocol. We
have HTTP for that. Put your models in files, fetch via HTTP and use
traditional techniques to break them up (e.g. Inlines and createX3DFromUrl)
and/or package multiple models into one file if you're worried about the
number of requests.


On Wed, Sep 1, 2010 at 2:55 AM, Sven-Erik Tiberg <Sven-Erik.Tiberg at ltu.se>wrote:

>  Hi Tony
> Watching an interesting video at
> http://www.infoq.com/presentations/Real-Time-Web-with-XMPP about XMPP in
> practice and using the Strophe http://code.stanziq.com/strophe/  js and C
> lib for event driven XMPP handler.
> Do you think that all X3D browsers could handle the Strophe.js scripts?
> That would be something :)
> Second I think that zlib could be involved in the transport of XMPP
> packages witch could be used to compact the messages and probably do some
> encryption on them but I'm not at all shure about this.
> On server / broker side they seem to use ejabberd in the presentation
> mentioned above, if so ejabberd are based in erlang that was constructed for
> telphone connections handling by ericsson and it's very fast in handling
> connections.
> Have a question, what form would be preferable for floating numerical data
> to be transport by using f.ex. XMPP?
> /Sven-Erik
>  ------------------------------
> *From:* Tony Parisi [mailto:tparisi at gmail.com]
> *Sent:* den 1 september 2010 02:47
> *To:* Sven-Erik Tiberg
> *Cc:* x3d-public at web3d.org
> *Subject:* Re: [X3D-Public] XMPP or not XMPP
> Hi Sven-Erik,
> I think you can do it. I was considering trying it as an alternate to our
> SWMP protocol at Vivaty. But I didn't get around to experimenting with it
> before um everything went blooey over there.
> I would be most concerned with response times for MU messages. XMPP was
> primarily designed to transport chat text. (I know it's more general than
> that but I'm talking about in a practical sense). Then again, networks keep
> getting faster so maybe response time is no longer an issue.
> There's also message size to worry about-- I am not sure what those limits
> are in XMPP, and you probably don't want to transfer LARGE messages for
> updates to scene graph state anyway. i.e. don't push IndexedFaceSets around
> in this fashion ;->
> So I say go for it. At least build a prototype, it will be worth the
> effort.
> Anyway, that's my $.02. I think it's still worth something even though the
> pennies are starting to oxidize a bit :-)
> Tony
> On Tue, Aug 31, 2010 at 10:33 AM, Sven-Erik Tiberg <
> Sven-Erik.Tiberg at ltu.se> wrote:
>>   Hi
>> Would like to know your opinion in using XMPP/Jabber as a
>> NetworkSensorNode type of transfering states between clients.
>> We are getting closer in forming a project with X3D-browsers and
>> simulation engines in a interactive space.
>> I would specially appreciate and argument against using this protocol.
>> BG
>> Sven-Erik Tiberg
>> Lulea Univ. of Technology.
>> Sweden
>> _______________________________________________
>> X3D-Public mailing list
>> X3D-Public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
> --
> Tony Parisi                             tparisi at gmail.com
> CTO at Large                         415.902.8002

Tony Parisi                             tparisi at gmail.com
CTO at Large                         415.902.8002
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20100901/7ac24236/attachment.html>

More information about the X3D-Public mailing list