Home Licence Credits Forum Please enter comments and feedback to info@bluehands.de Issue Tracking (public disabled) Info MyJingle is a sample program based on LibJingle. It was created while adding VoIP to LLuna. MyJingle is a test program. Its main purpose is to learn LibJingle using VS 2005 during complete peer to peer sessions. MyJingle shows how to use LibJingle on Windows in
libjingle License Agreement libjingle Copyright 2004--2007, Google Inc. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above co
A blog about voice, IM and open communications with Google Talk. I've been following all the buzz over the weekend in the blogosphere about the Libjingle release. You can check it out for yourself using Google Blog Search. I'm very pleased with all the excitement about what this technology can enable. However, when I read this post I realized that many of our users may not be clear on exactly what
Posted on 9æ 20, 2008 Filed Under ice, xmpp, stun, udp, P2P | XMPPã§P2Pã®é³å£°ãã£ããã»ãã·ã§ã³ã確ç«ããæ¹æ³2 ããã®ç¶ãã XEP-0176: Jingle ICE-UDP Transport Method ãèªãã This specification defines a Jingle transport method that results in sending media data using raw datagram sockets via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodolo
ã®ä¸èº«ã¯ XEP-0166: Jingle ã§ã¯æ±ã£ã¦ãªãã XEP-0166ã®ä¸ã§ã Naturally, more complex scenarios are probable; such scenarios are described in other specifications, such as XEP-0167 for voice chat. ã£ã¦ã®ãããã®ã§ãã¤ã³ã¿ã®å ã«é£ãã§ã¿ã XEP-0167: Jingle RTP Sessions This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voi
AbstractThis specification defines an XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities in a way that is interoperable with existing Internet standards. The protocol provides a pluggable model that enables the core session management semantics (compatible with SIP) to be used for a wide variety of application types (e.g., voice chat, video ch
Posted on 9æ 20, 2008 Filed Under jingle, xmpp, libjingle, nat, P2P | é ãæ´çããããã®Memo GoogleTalkã§ä½¿ããã¦ããã¨ããjingle XEP-0166: Jingle XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities in a way that is interoperable with existing Internet standards æ¢åã®Internetæ¨æºã¨å ±åã§ããæ¹æ³ã§ãï¼ã¤ã®XMPPentitieséã§P2Pã¡ãã£ã¢ã»ãã·ã§ã³ã確ç«ã管çããããã®XMPPãããã³ã«ã®æ¡å¼µã In essence, Jingle en
About libjingle libjingle is a collection of open-source C++ code and sample applications that enables you to build a peer-to-peer application. The code handles creating a network connection (through NAT and firewall devices, relay servers, and proxies), negotiating session details (codecs, formats, etc.), and exchanging data. It also provides helper tasks such as parsing XML, and handling network
å©ç¨æ¹æ³ 1. Google ãã¼ã¯ ãããããã¼ ããã¥ã¡ã³ãã確èªãã¾ãã 2. ã¯ã©ã¤ã¢ã³ãããã«ããã¦ãµã¼ãã¹ã Google ãã¼ã¯ã«æ¥ç¶ããããã¦ã§ããã¼ã¸ã«ã¯ã©ã¤ã¢ã³ããåãè¾¼ã¿ã¾ãã Google ãã¼ã¯ã«ã¤ã㦠Google ãã¼ã¯ã¯ãªã¼ãã³ ãããã³ã«ä¸ã«æ§ç¯ãããã¤ã³ã¹ã¿ã³ã ã¡ãã»ã¼ã¸ã³ã° ãµã¼ãã¹ã§ããGoogle ã IM ãµã¼ãã¹ãéè¨ããã®ã¯ãã¦ã¼ã¶ã¼ãç¬èªã®ã¯ã©ã¤ã¢ã³ã ã¢ããªã±ã¼ã·ã§ã³ã Google ãã¼ã¯ ãµã¼ãã¹ã«ããã¯ãããããµã¼ãã¹ã Google ã®ãµã¼ãã¹ã«æ¥ç¶ (ãã§ãã¬ã¼ã) ãããã§ããããã«ããããã§ãã Google ãã¼ã¯ ãµã¼ãã¹ã¯ã次ã®ãªã¼ãã³ã½ã¼ã¹ ãããã³ã«ä¸ã«æ§ç¯ããã¦ãã¾ãã XMPP: Extensible Messaging and Presence Protocol ã®ç¥ã§ãã¤ã³ã¹ã¿ã³ã ã¡ãã»ã¼ã¸ã³ã°ã®
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}