mirror of
https://codeberg.org/Mercury-IM/Smack
synced 2025-12-07 13:41:08 +01:00
s/ a XMPP/ an XMPP/
This commit is contained in:
parent
a927d55bb1
commit
57c1b57b7c
32 changed files with 53 additions and 53 deletions
|
|
@ -97,7 +97,7 @@ import org.jxmpp.util.XmppStringUtils;
|
|||
* <p/>
|
||||
* try {
|
||||
* <p/>
|
||||
* // Connect to a XMPP Server
|
||||
* // Connect to an XMPP Server
|
||||
* XMPPConnection x1 = new XMPPTCPConnection("xmpp.com");
|
||||
* x1.connect();
|
||||
* x1.login("juliet", "juliet");
|
||||
|
|
@ -140,7 +140,7 @@ import org.jxmpp.util.XmppStringUtils;
|
|||
* <p/>
|
||||
* try {
|
||||
* <p/>
|
||||
* // Connect to a XMPP Server
|
||||
* // Connect to an XMPP Server
|
||||
* XMPPConnection x0 = new XMPPTCPConnection("xmpp.com");
|
||||
* x0.connect();
|
||||
* x0.login("romeo", "romeo");
|
||||
|
|
@ -250,7 +250,7 @@ public class JingleManager implements JingleSessionListener {
|
|||
/**
|
||||
* Setup the jingle system to let the remote clients know we support Jingle.
|
||||
* (This used to be a static part of construction. The problem is a remote client might
|
||||
* attempt a Jingle connection to us after we've created a XMPPConnection, but before we've
|
||||
* attempt a Jingle connection to us after we've created an XMPPConnection, but before we've
|
||||
* setup an instance of a JingleManager. We will appear to not support Jingle. With the new
|
||||
* method you just call it once and all new connections will report Jingle support.)
|
||||
*/
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ public class BridgedResolver extends TransportResolver {
|
|||
|
||||
/**
|
||||
* Constructor.
|
||||
* A Bridged Resolver need a XMPPConnection to connect to a RTP Bridge.
|
||||
* A Bridged Resolver need an XMPPConnection to connect to a RTP Bridge.
|
||||
*/
|
||||
public BridgedResolver(XMPPConnection connection) {
|
||||
super();
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ import de.javawi.jstun.util.UtilityException;
|
|||
/**
|
||||
* ICE Resolver for Jingle transport method that results in sending data between two entities using the Interactive Connectivity Establishment (ICE) methodology. (XEP-0176)
|
||||
* The goal of this resolver is to make possible to establish and manage out-of-band connections between two XMPP entities, even if they are behind Network Address Translators (NATs) or firewalls.
|
||||
* To use this resolver you must have a STUN Server and be in a non STUN blocked network. Or use a XMPP server with public IP detection Service.
|
||||
* To use this resolver you must have a STUN Server and be in a non STUN blocked network. Or use an XMPP server with public IP detection Service.
|
||||
*
|
||||
* @author Thiago Camargo
|
||||
*/
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue