Subject: Voice Calling for Psi
Ok, publicising my blog shamelessly again:
http://www.kismith.co.uk/wordpress/index.php/2005/12/16/i-…
A summary:
The Jingle protocol (session and voice) is the culmination of months of discussion between the Google Talk team and interested parties in the JSF, which finally became standards-track yesterday. Jingle is basically the voice protocol supported by the Google Talk client.
The Google Talk team today announced the first release of a C++ library which manages the Jingle protocol. This means that other clients should be able to take this code and integrate Jingle support without coding the p2p and other details themselves.
In the last month or so, Sean Egan (one of the nice guys on the GT team (yes, they rock)) has been helping Remko and myself integrate the libjingle code in Psi ready for libjingle’s release today, meaning……voice calling for Psi. This is where a lot of Remko and my time has gone which might otherwise have been spent on visible Psi development.
http://www.kismith.co.uk/wordpress/index.php/2005/12/16/i-…
A summary:
The Jingle protocol (session and voice) is the culmination of months of discussion between the Google Talk team and interested parties in the JSF, which finally became standards-track yesterday. Jingle is basically the voice protocol supported by the Google Talk client.
The Google Talk team today announced the first release of a C++ library which manages the Jingle protocol. This means that other clients should be able to take this code and integrate Jingle support without coding the p2p and other details themselves.
In the last month or so, Sean Egan (one of the nice guys on the GT team (yes, they rock)) has been helping Remko and myself integrate the libjingle code in Psi ready for libjingle’s release today, meaning……voice calling for Psi. This is where a lot of Remko and my time has gone which might otherwise have been spent on visible Psi development.


Kev
Show profile
Link to this post

