erichocean / libjingle

Automatically exported from code.google.com/p/libjingle
0 stars 0 forks source link

No implementation of google:jingleinfo #161

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What is the expected output? What do you see instead?
Google has defined a non-standard extension for STUN servers, "Jingle Server 
DIscovery" with feature specified using namespace google:jingleinfo.
 http://code.google.com/apis/talk/jep_extensions/jingleinfo.html

While this namespace is mentioned in constants.cc, it is currently unused 
elsewhere, leading to the conclusion that the library does not automatically 
attempt to discover STUN servers, which may be useful for Google's services, as 
well as third-party supporting servers.

There is also a currently deferred XEP which serves the same purpose; this is 
XEP-0215:
 http://xmpp.org/extensions/xep-0215.html

Original issue reported on code.google.com by ivuc...@gmail.com on 7 May 2011 at 12:43

GoogleCodeExporter commented 9 years ago
This is not completely true. The "google:jingleinfo" namespace is used in the 
following places:
const std::string NS_JINGLE_INFO("google:jingleinfo");
const QName QN_JINGLE_INFO_QUERY(true, NS_JINGLE_INFO, "query");
const QName QN_JINGLE_INFO_STUN(true, NS_JINGLE_INFO, "stun");
const QName QN_JINGLE_INFO_RELAY(true, NS_JINGLE_INFO, "relay");
const QName QN_JINGLE_INFO_SERVER(true, NS_JINGLE_INFO, "server");
const QName QN_JINGLE_INFO_TOKEN(true, NS_JINGLE_INFO, "token");

Original comment by jun...@google.com on 23 May 2011 at 10:00