Difference between revisions of "Stream Initiation (XEP-0095)"

From XMPP WIKI
Jump to navigation Jump to search
m (JEP->XEP)
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{xep}}
+
{{remarks}}
  
 
Alex Wenckus [http://thread.gmane.org/gmane.network.jabber.standards-jig/10468 proposed] a way to implement fall-over between different kinds of stream methods.  That is, if establishing a SOCKS5 connection fails, clients should be able to use an IBB instead without starting a new SI session.  This method is implemented by: (feel free to complete the list)
 
Alex Wenckus [http://thread.gmane.org/gmane.network.jabber.standards-jig/10468 proposed] a way to implement fall-over between different kinds of stream methods.  That is, if establishing a SOCKS5 connection fails, clients should be able to use an IBB instead without starting a new SI session.  This method is implemented by: (feel free to complete the list)
Line 5: Line 5:
 
* [http://www.jivesoftware.org/spark/ Spark]
 
* [http://www.jivesoftware.org/spark/ Spark]
  
There are proposed additions to [[SOCKS5_Bytestreams_(JEP-0065)|XEP-0065]] as well, that make connection success more likely.
+
There are proposed additions to [[SOCKS5_Bytestreams_(XEP-0065)|XEP-0065]] as well, that make connection success more likely.

Latest revision as of 17:48, 10 October 2019

This is a page for information about Stream Initiation (XEP-0095), including errata, comments, questions, and implementation experience.

Alex Wenckus proposed a way to implement fall-over between different kinds of stream methods. That is, if establishing a SOCKS5 connection fails, clients should be able to use an IBB instead without starting a new SI session. This method is implemented by: (feel free to complete the list)

There are proposed additions to XEP-0065 as well, that make connection success more likely.