mirror of
https://codeberg.org/Mercury-IM/Smack
synced 2025-09-09 10:19:41 +02:00
Merge branch '4.0'
Conflicts: build.gradle documentation/connections.html documentation/gettingstarted.html smack-core/src/main/java/org/jivesoftware/smack/SmackException.java smack-core/src/test/java/org/jivesoftware/smack/parsing/ParsingExceptionTest.java smack-core/src/test/java/org/jivesoftware/smack/test/util/TestUtils.java smack-core/src/test/java/org/jivesoftware/smack/util/PacketParserUtilsTest.java smack-extensions/src/main/java/org/jivesoftware/smackx/caps/cache/SimpleDirectoryPersistentCache.java smack-extensions/src/main/java/org/jivesoftware/smackx/ping/PingManager.java smack-tcp/src/main/java/org/jivesoftware/smack/tcp/PacketReader.java
This commit is contained in:
commit
94a16ba41e
61 changed files with 806 additions and 300 deletions
|
@ -16,8 +16,8 @@ Debugging with Smack
|
|||
|
||||
<p>
|
||||
Smack includes two built-in debugging consoles that will let you track all XML traffic between
|
||||
the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack.jar</tt>
|
||||
and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smackx-debug.jar</tt>.
|
||||
the client and server. A <a href="#lite">lite debugger</a> which is part of the <tt>smack-core.jar</tt>
|
||||
and an <a href="#enhanced">enhanced debugger</a> contained in <tt>smack-debug.jar</tt>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -56,7 +56,7 @@ Smack uses the following logic to decide the debugger console to use:
|
|||
<li>If step 1 fails then Smack will try to use the enhanced debugger. The
|
||||
file <tt>smackx-debug.jar</tt> contains the enhanced debugger. Therefore you will need
|
||||
to place the jar file in the classpath. For situations where space is an issue you
|
||||
may want to only deploy <tt>smack.jar</tt> in which case the enhanced debugger won't be
|
||||
may want to only deploy <tt>smack-core.jar</tt> in which case the enhanced debugger won't be
|
||||
available.<p>
|
||||
|
||||
<li>The last option if the previous two steps fail is to use the lite debugger. The lite
|
||||
|
|
|
@ -15,7 +15,7 @@ tasks such as registration and searching using Forms.
|
|||
<li><a href="#gather">Create a Form to fill out</a></li>
|
||||
<li><a href="#fillout">Answer a Form</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0004.html">JEP-4</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0004.html">XEP-4</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -18,7 +18,7 @@ entities. Follow these links to learn how to use this extension.
|
|||
<li><a href="#discoinfo">Discover information about an XMPP entity</a></li>
|
||||
<li><a href="#discopublish">Publish publicly available items</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0030.html">JEP-30</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0030.html">XEP-30</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -17,10 +17,10 @@ The file transfer extension allows the user to transmit and receive files.
|
|||
<li><a href="#recievefile">Recieving a file from another user</a></li>
|
||||
<li><a href="#monitorprogress">Monitoring the progress of a file transfer</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0095.html">JEP-95</a>
|
||||
<a href="http://www.jabber.org/jeps/jep-0096.html">JEP-96</a>
|
||||
<a href="http://www.jabber.org/jeps/jep-0065.html">JEP-65</a>
|
||||
<a href="http://www.jabber.org/jeps/jep-0047.html">JEP-47</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0095.html">XEP-95</a>
|
||||
<a href="http://www.xmpp.org/extensions/xep-0096.html">XEP-96</a>
|
||||
<a href="http://www.xmpp.org/extensions/xep-0065.html">XEP-65</a>
|
||||
<a href="http://www.xmpp.org/extensions/xep-0047.html">XEP-47</a>
|
||||
<hr>
|
||||
|
||||
<div class="subheader"><a name="sendfile">Send a file to another user</a></div><p>
|
||||
|
|
|
@ -32,17 +32,17 @@
|
|||
</tr>
|
||||
<tr>
|
||||
<td><a href="messageevents.html">Message Events</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0022.html">JEP-0022</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0022.html">XEP-0022</a></td>
|
||||
<td>Requests and responds to message events.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="dataforms.html">Data Forms</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0004.html">JEP-0004</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0004.html">XEP-0004</a></td>
|
||||
<td>Allows to gather data using Forms.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="muc.html">Multi User Chat</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0045.html">JEP-0045</a></td>
|
||||
<td><a href="http://www.xmpp.org/extensions/xep-0045.html">XEP-0045</a></td>
|
||||
<td>Allows configuration of, participation in, and administration of individual text-based conference rooms.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
|
|
@ -17,8 +17,8 @@ users to a group chat room.
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
<b>JEP related:</b> N/A -- this protocol is outdated now that the Multi-User Chat (MUC) JEP is available
|
||||
(<a href="http://www.jabber.org/jeps/jep-0045.html">JEP-45</a>). However, most
|
||||
<b>XEP related:</b> N/A -- this protocol is outdated now that the Multi-User Chat (MUC) XEP is available
|
||||
(<a href="http://www.xmpp.org/extensions/xep-0045.html">XEP-45</a>). However, most
|
||||
existing clients still use this older protocol. Once MUC support becomes more
|
||||
widespread, this API may be deprecated.
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ display, and composition of messages. There are three stages in this extension:<
|
|||
<li><a href="#lstevnotreq">Reacting to Event Notification Requests</a></li>
|
||||
<li><a href="#lstevnot">Reacting to Event Notifications</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0022.html">JEP-22</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0022.html">XEP-22</a>
|
||||
<hr>
|
||||
<div class="subheader"><a name="reqevnot">Requesting Event Notifications</a></div><p>
|
||||
<b>Description</b><p>
|
||||
|
|
|
@ -22,7 +22,7 @@ Allows configuration of, participation in, and administration of individual text
|
|||
<li><a href="#role">Manage role modifications</a></li>
|
||||
<li><a href="#afiliation">Manage affiliation modifications</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0045.html">JEP-45</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0045.html">XEP-45</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ XML namespace. Example private data:
|
|||
</color>
|
||||
</pre><p>
|
||||
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0049.html">JEP-49</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0049.html">XEP-49</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ are received from other XMPP clients.
|
|||
<li><a href="#riesendentry">Send a roster's entry</a></li>
|
||||
<li><a href="#riercventry">Receive roster entries</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0093.html">JEP-93</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0093.html">XEP-93</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
Supports a protocol that XMPP clients use to exchange their respective local
|
||||
times and time zones.<p>
|
||||
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0090.html">JEP-90</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0090.html">XEP-90</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -18,7 +18,7 @@ XHTML messages:</p>
|
|||
<li><a href="#xhtmlreceive">Receive an XHTML Message</a></li>
|
||||
<li><a href="#xhtmldiscover">Discover support for XHTML Messages</a></li>
|
||||
</ul>
|
||||
<b>JEP related:</b> <a href="http://www.jabber.org/jeps/jep-0071.html">JEP-71</a>
|
||||
<b>XEP related:</b> <a href="http://www.xmpp.org/extensions/xep-0071.html">XEP-71</a>
|
||||
|
||||
<hr>
|
||||
|
||||
|
|
|
@ -29,8 +29,8 @@ to be as small as possible. The library ships as several JAR files to provide mo
|
|||
over which features applications require:
|
||||
|
||||
<ul>
|
||||
<li><tt>smack-core.jar</tt> -- provides core XMPP functionality and is the only <b>required</b>
|
||||
library. All XMPP features that are part of the XMPP RFCs are included.</li>
|
||||
<li><tt>smack-core.jar</tt> -- provides core XMPP functionality. All XMPP features that are
|
||||
part of the XMPP RFCs are included.</li>
|
||||
<li><tt>smack-extensions.jar</tt> -- support for many of the extensions (XEPs) defined
|
||||
by the XMPP Standards Foundation, including multi-user chat, file transfer, user search, etc.
|
||||
The extensions are documented in the <a href="extensions/index.html">extensions manual</a>.</li>
|
||||
|
@ -52,7 +52,6 @@ over which features applications require:
|
|||
is enabled.</li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p class="subheader">Configuration</p>
|
||||
Smack has an initialization process that involves 2 phases.
|
||||
<ul>
|
||||
|
|
|
@ -28,7 +28,7 @@ Smack Key Advantages
|
|||
can be accomplished in only a few lines of code:
|
||||
|
||||
<div class="code"><pre>
|
||||
Connection connection = <font color="navy"><b>new</b></font> XMPPConnection(<font color="green">"jabber.org"</font>);
|
||||
XMPPConnection connection = <font color="navy"><b>new</b></font> XMPPTCPConnection(<font color="green">"jabber.org"</font>);
|
||||
connection.connect();
|
||||
connection.login(<font color="green">"mtucker"</font>, <font color="green">"password"</font>);
|
||||
Chat chat = connection.getChatManager().createChat(<font color="green">"jsmith@jivesoftware.com"</font>, new MessageListener() {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue