> I dont think this is a good idea. Sipxtapi is not fast enough for what> you
> need. You should support transport over udp/tcp/tls/http tunneling,> with C++
> object serialization and virtual channels. In java something> like this is
> easy to do, but in C++ you will have more work with it.> > Jaro
Sorry, but I forgot to mention that these will all be turn-based games. So
speed isn't *that* critical. But then again, if there are no benefits from
using sipxtapi (or using SIP as a communication protocol), then obviously there
is no point in doing that.
Jaro, when you talk about udp/tcp/tls/http tunneling and virtual channels, have
you got any particular implementation in mind? Any similar frameworks you would
recommend checking out?
Regards,
DanÃel
> Date: Tue, 14 Aug 2007 19:15:49 +0200> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> CC: [email protected]> Subject: Re: [sipxtapi-dev]
> Extending sipxtapi> > Daniel Sigurgeirsson wrote:> > > > Hi all,> > > > I
> have a general question regarding the usage of sipxtapi. I've been> >
> thinking if SIP (and hopefully sipxtapi) could be used as a> > communication
> protocol for an application I would like to write. The> > idea is to create a
> gaming application, where people can play various> > multiplayer table-based
> games (similar to RISK, and other not-so-similar> > games), where new games
> could be added to the application without too> > much hassle. The question
> is: would I gain anything by using SIP as the> > base protocol, and then use
> different protocol for transmission of the> > game data? If so, does sipxtapi
> support something like this? I.e. is it> > easy to "plug in" different
> protocols into it (protocols which may or> > may not transmit audio/video
> data, probably just game-specific data), or> > is that perhaps not necessary
> at all? Obviously sipxtapi cannot know> > about all possible protocols, so
> I'm just trying to figure out how hard> > it is to use other protocols
> alongside SIP, if I would have to write the> > complete networking part
> myself or if sipxtapi would help with some> > parts of it.> > > > I'm just
> thinking out loud here, I haven't thought this through by any> > means, and
> therefore I would welcome any comments whatsoever.> > > > Regards,> > Daniel>
> > > > I dont think this is a good idea. Sipxtapi is not fast enough for what>
> you need. You should support transport over udp/tcp/tls/http tunneling,> with
> C++ object serialization and virtual channels. In java something> like this
> is easy to do, but in C++ you will have more work with it.> > Jaro
_________________________________________________________________
Connect to the next generation of MSN MessengerÂ
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
