x1740.htm

Its a xmpp protocol book

><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Condition</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Example</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Description</TH
></TR
></THEAD
><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;ns/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;ns&#62;jabber:iq:version&#60;/ns&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the namespace ('ns') of an 
<TT
CLASS="LITERAL"
>&#60;iq/&#62;</TT
>
packet.

<A
NAME="JABTDG-CH-4-FOOTNOTE-8"
HREF="#FTN.JABTDG-CH-4-FOOTNOTE-8"
>[a]</A
>&#13;</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;unavailable/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;unavailable/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches when the recipient's presence type is 'unavailable'.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;from/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;from&#62;[e-mail]&#60;/from&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the sender's Jabber ID (JID) - user@host.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;resource/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;resource&#62;Work&#60;/resource&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the recipient's resource. </TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;subject/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;subject&#62;Work(!)&#60;/subject&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the message's subject (in the 
<TT
CLASS="LITERAL"
>&#60;subject/&#62;</TT
>
tag) - must match exactly.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;body/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;body&#62;Are you there?&#60;/body&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the message content  (in the 
<TT
CLASS="LITERAL"
>&#60;body/&#62;</TT
>
tag) - must match exactly.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;show/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;show&#62;dnd&#60;/show&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the recipient's presence 'show' - usually one of 
<I
CLASS="EMPHASIS"
>normal</I
> (the default),
<I
CLASS="EMPHASIS"
>chat</I
>,
<I
CLASS="EMPHASIS"
>away</I
>,
<I
CLASS="EMPHASIS"
>xa</I
> (eXtended Away) or
<I
CLASS="EMPHASIS"
>dnd</I
> (Do Not Disturb).</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;type/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;type&#62;chat&#60;/type&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches the type of the incoming message (in the <TT
CLASS="OPTION"
>type=""</TT
>
attribute) - could be one of
<I
CLASS="EMPHASIS"
>normal</I
>,
<I
CLASS="EMPHASIS"
>chat</I
>,
<I
CLASS="EMPHASIS"
>headline</I
> or
<I
CLASS="EMPHASIS"
>error</I
>.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;roster/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;roster/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches if the sender is in the recipient's roster.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;group/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;group&#62;Friends&#60;/group&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Matches if the sender is in a particular group in the recipient's roster.</TD
></TR
></TBODY
><TR
><TD
COLSPAN="3"
>Notes:<BR><A
NAME="FTN.JABTDG-CH-4-FOOTNOTE-8"
>a. </A
>The name "message filter service" is slightly inaccurate as incoming
<TT
CLASS="LITERAL"
>&#60;iq/&#62;</TT
> (Info/Query)
packets can also be filtered - and the matching takes place on the
namespace described in the <TT
CLASS="OPTION"
>xmlns=""</TT
> attribute.<BR></TD
></TR
></TABLE
></DIV
><DIV
CLASS="TABLE"
><A
NAME="JABTDG-CH-4-TABLE-2"
></A
><P
><B
>Table 4-2. Filter actions</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><THEAD
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Action</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Example</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Description</TH
></TR
></THEAD
><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;error/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;error&#62;Address defunct&#60;/error&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Sends an error reply to the sender.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;offline/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;offline/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Stores the incoming message offline. The recipient will receive it
the next time he logs on.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;forward/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;forward&#62;colleague@server&#60;/forward&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>The message will be forwarded to another Jabber ID (JID).</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;reply/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;reply&#62;Be right back!&#60;/reply&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>A reply will be sent to the sender.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;settype/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;settype&#62;normal&#60;/settype&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Changes the type of the incoming message (see 
<TT
CLASS="LITERAL"
>&#60;type/&#62;</TT
>
in the Conditions table above).</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;continue/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TT
CLASS="LITERAL"
>&#60;continue/&#62;</TT
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Special action to continue on to the next rule.</TD
></TR
></TBODY
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="JABTDG-CH-4-SECT-4.3.1.3.2"
>Server vCard</A
></H4
><P
>Every user can maintain a virtual business card - a vCard - which is stored
server-side. vCards can be retrieved at any time by any user. The 
<TT
CLASS="LITERAL"
>&#60;vCard/&#62;</TT
>
tag here in the jsm configuration gives the Jabber server an identity - 
its vCard can be retrieved also.</P
><P
>You can maintain the server's vCard data in this part of the jsm configuration:</P
><P
><PRE
CLASS="SCREEN"
>&#60;vCard&#62;
  &#60;FN&#62;Jabber Server on yak&#60;/FN&#62;
  &#60;DESC&#62;A Jabber Server!&#60;/DESC&#62;
  &#60;URL&#62;http://yak/&#60;/URL&#62;
&#60;/vCard&#62;</PRE
></P
><P
>All the vCard elements can be used for this vCard configuration, not
just the ones shown here.</P
></DIV
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="JABTDG-CH-4-SECT-4.3.1.3.3"
>Registration Instructions</A
></H4
><P
>Registration instructions such as those defined here:</P
><P
><PRE
CLASS="SCREEN"
>&#60;register notify="yes"&#62;
  &#60;instructions&#62;Choose a userid and password to register.&#60;/instructions&#62;
  &#60;name/&#62;
  &#60;email/&#62;
&#60;/register&#62;</PRE
></P
><P
>are available to whoever asks for them; in its
most formal state, the procedure for creating a new user account on a Jabber
server includes a first step of asking the server what is required for
the registration process.</P
><P
>The registration service is provided by the <TT
CLASS="LITERAL"
>mod_register</TT
> module. </P
><P
>In reply to such a request (which is made with an 
<TT
CLASS="LITERAL"
>&#60;iq/&#62;</TT
>
get request in the <TT
CLASS="LITERAL"
>jabber:iq:register</TT
>
namespace - see Part II for details) the instructions and a list of 
required fields are returned by <TT
CLASS="LITERAL"
>mod_register</TT
>.
Note that the list of fields provided in this 
<TT
CLASS="LITERAL"
>&#60;register/&#62;</TT
>
section are over and above the standard required fields required in any
case for registration:</P
><P
></P
><UL
><LI
><P
><TT
CLASS="LITERAL"
>&#60;username/&#62;</TT
></P
></LI
><LI
><P
><TT
CLASS="LITERAL"
>&#60;password/&#62;</TT
></P
></LI
></UL
><P
>so that in this particular configuration case both
<TT
CLASS="LITERAL"
>&#60;name/&#62;</TT
>
and
<TT
CLASS="LITERAL"