"Remko Tronçon" <[EMAIL PROTECTED]> writes: > I don't really get how it works (or is supposed to work). Can you > explain it a bit?
The client does what it is good at - slinging XML back and forth. When it needs to set up a Jingle session, it asks the component to do so, relaying the necessary details over D-Bus. The component opens the audio device and connects to the other party, hiding all such details from the client. This is essential to jabber.el, as it is unable to load libraries, but other clients could use such a component as well. The current status is that Tox can tell the client which codecs it supports, which the client then uses to send the initial Jingle stanza. Doing the actual connection comes next... -- Magnus JID: [EMAIL PROTECTED]
