[Standards-JIG] Re: VoIP Jabber

[Richard Dobson]

> What we are exactly thinking about, is to make the component as a process 
> (available on windows, linux and macosx) that an xmpp-client executes and 
> which communicates with (for control and notification purposes) through 
> pipe or soap or xml-rpc (or another kind of interprocess communication): 
> if a given user has more then one jabber client installed, each one will 
> execute the version of this engine it is shipped with.

That sounds better, at least its not a windows service which is what you 
seemed to indicate in your previous email.

> The main advantage is that, since its loose coupling, this "service" can

Its more of a "module" that a "service", service suggests it will be running 
all the time whether the client was or not.

> be integrated in almost every jabber client out there (of course the 
> communication will be somehow tricky for ALL); on the other side, future 
> enhancements like including video support could be almost impossible 
> (since you have to be in-process to create a child window).

That is a problem.

> Maybe a list of client developers interested at working (or already 
> working) with voice integration, with a short description of their 
> thoughts about this issue, could enrich this discussion.

Yup I am one of those said people, just waiting for a spec to be finalised 
for in-client voice, thats mainly what is holding me back, at the moment 
looking at the best way to implement RTP support in my client, which is the 
one part that seems to have been agreed upon (i.e. the use of RTP for the 
voice data transport).

Richard