On Wed, Mar 26, 2008 at 05:34:53PM +0100, Magnus Henoch wrote:
Sjoerd Simons [EMAIL PROTECTED] writes:
Why not use the Telepatmy XMPP client ? :)
Because the thing I enjoy most about writing an XMPP client is being
able to hack new protocols and features along with the UI. It seems to
On Tue, Mar 25, 2008 at 09:17:50PM +0100, Magnus Henoch wrote:
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
Sjoerd Simons [EMAIL PROTECTED] writes:
What your describing here is basically the way Telepathy works. See
http://telepathy.freedesktop.org/wiki/Streamed_Media for a global view of how
VOIP works with systems using telepathy.
Indeed, I'm building such a stream engine. Would the Telepathy
Magnus Henoch wrote:
Sjoerd Simons [EMAIL PROTECTED] writes:
What your describing here is basically the way Telepathy works. See
http://telepathy.freedesktop.org/wiki/Streamed_Media for a global view of how
VOIP works with systems using telepathy.
Indeed, I'm building such a stream
On Tue, Mar 25, 2008 at 9:17 PM, Magnus Henoch mange-at-freemail.hu
|jdev2| ... wrote:
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
On Wed, Mar 26, 2008 at 02:52:37PM +0100, Magnus Henoch wrote:
Sjoerd Simons [EMAIL PROTECTED] writes:
What your describing here is basically the way Telepathy works. See
http://telepathy.freedesktop.org/wiki/Streamed_Media for a global view of
how
VOIP works with systems using
Sjoerd Simons [EMAIL PROTECTED] writes:
Why not use the Telepatmy XMPP client ? :)
Because the thing I enjoy most about writing an XMPP client is being
able to hack new protocols and features along with the UI. It seems to
me that when writing a Telepathy client I would be restricted to the UI
Massimiliano Mirra [EMAIL PROTECTED] writes:
Today, I'm wondering whether a simple, specialized process to which
the main client forwards Jingle-related XMPP stanzas to, using a local
TCP connection, is the easiest/most portable way to do it.
Essentially like jinglepipe but over a socket.
Today, I'm wondering whether a simple, specialized process to which
the main client forwards Jingle-related XMPP stanzas to, using a local
TCP connection, is the easiest/most portable way to do it.
Essentially like jinglepipe but over a socket.
Certainly most portable (modulo how
I just wrote a proposal for a GSoC project on the wiki:
http://wiki.jabber.org/index.php/Summer_of_Code_2008#Client-Independent_D-Bus_Service_for_Jingle_Audio
From previous inquiries I have found that I'm probably the only person
enthusiastic about that, but in case I'm wrong: would someone be
From previous inquiries I have found that I'm probably the only person
enthusiastic about that, but in case I'm wrong
I don't really get how it works (or is supposed to work). Can you
explain it a bit?
cheers,
Remko
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
12 matches
Mail list logo
