91免费精品国自产拍在线不卡,久久亚洲精品中文字幕,日本在线三级

XMPP初解

飛雪(leo) — Sun, 31 Dec 2006 05:17:00 GMT

1、什么是XMPP �Q?br />XMPP�Q�即Extensible Messaging and Presence Protocol�Q�其前��n是Jabber�Q�一个开源�Ş式组�l��生的�|�络��x��通信协议。XMPP目前被IETF国际标准�l�织完成了标准化工作。标准化的核心结果分��Z��部分�Q?
核心的XML��传输协�?
��Z��XML��传输的��x��通讯扩展应用
XMPP的核心XML��传输协议的定义使得XMPP能够在一个比以往�|�络通信协议更规范的�q�_��上。借助于XML易于解析和阅�ȝ��Ҏ��，使得XMPP的协议能够非常漂亮�?
XMPP的即旉��讯扩展应用部分是根据IETF在这之前对即旉��讯的一个抽象定义的�Q�与其他业已得到�q�泛使用的即旉��讯协议�Q�诸如AIM�Q�QQ�{�有功能完整�Q�完善等先进性�?

2、XMPP的基本网�l�结构是怎样的？
XMPP中定义了三个角色�Q�客��L��Q�服务器�Q�网兟뀂通信能够在这三者的��L��两个之间双向发生。服务器同时承担了客��L��信息记录�Q�连接管理和信息的�\由功能。网��x��担着与异构即旉��信�pȝ��的互联互通，异构�pȝ��可以包括SMS�Q�短信）�Q�MSN�Q�ICQ�{�。基本的�|�络形式是单客户端通过TCP/IP�q�接到单服务器，然后在之上传输XML�?

3、XMPP通过TCP传什么了�Q?
传输的是与即旉��讯相关的指令。在以前�q�些命��o要么�?�q�制的�Ş式发送（比如QQ�Q�，要么用纯文本指��o加空格加参数加换行苻的方式发送（比如MSN�Q�。而XMPP传输的即旉��讯指��o的逻辑与以往�总��Q�只是协议的形式变成了XML格式的纯文本。这不但使得解析�Ҏ��了，��Z��Ҏ��阅读了，方便了开发和查错。而XMPP的核心部分就是一个在�|�络上分片断发送XML的流协议。这个流协议是XMPP的即旉��讯指��o的传递基��Q�也是一个非帔R��要的可以被进一步利用的�|�络基础协议。所以可以说�Q�XMPP用TCP传的是XML��?

4、�D个例子看看所谓的XML��是什么样子的�Q?
客户端：
              to='example.com'
       xmlns='jabber:client'
       xmlns:stream='http://etherx.jabber.org/streams'
       version='1.0'>
服务器：
              from='example.com'
       id='someid'
       xmlns='jabber:client'
       xmlns:stream='http://etherx.jabber.org/streams'
       version='1.0'>
...其他通信...
客户端：from='juliet@example.com'
              to='romeo@example.net'
              xml:lang='en'>
客户端： Art thou not Romeo, and a Montague?
客户端：
服务器： from='romeo@example.net'
              to='juliet@example.com'
              xml:lang='en'>
服务器：Neither, fair saint, if either thee dislike.
服务器：
客户端：
服务器：
以文档的观点来看�Q�客��L��或服务器发送的所有XML文本�q�缀在一��P��?lt;stream>�?lt;/stream>构成了一个完整的XML文档。其中的stream标签��是所谓的XML Stream。在�?lt;/stream>中间的那�?lt;message>...�q�样的XML元素��是所谓的XML Stanza�Q�XML节）。XMPP核心协议通信的基本模式就是先建立一个stream�Q�然后协商一堆安全之�cȝ��东西�Q�中间通信�q�程��是客户端发送XML Stanza�Q�一个接一个的。服务器�Ҏ��客户端发送的信息以及�E�序的逻辑�Q�发送XML Stanza�l�客��L��。但是这个过�E��ƈ不是一问一�{�的�Q��Q何时候都有可能从一个方发信�l�另外一斏V��通信的最后阶�D�|��关闭��，关闭TCP/IP�q�接�?
GTalk所遵��@的协�?--XMPP

前几天Google发布了一�Ƒ֐�叫Google Talk的即旉��讯软�g�Q�这�ƾ��Y件的买点卖点之一��是XMPP。那�Q�什么是XMPP呢？
　　可扩展通讯和表�C�协�?(XMPP) 可用于服务类实时通讯、表�C�和需�?- 响应服务中的 XML 数据元流式传输。XMPP �?Jabber 协议为基��Q��?Jabber 是即旉��讯中常用的开攑ּ�协议�?br />　　 ��管 XMPP 没有完全溶合�q��Q何特定的�|�络架构之中�Q�但是通过客户�?服务器架构，它还是经常被采用�Q�因为客��h��需要��?XMPP �l�过 TCP �q�接讉K��服务器，而服务器之间也是通过 TCP �q�接�q�行通信的。服务器可�v�?XMPP 通讯的智能提取层的作用。许多客��h��直接通过 TCP �q�接与服务器相连�Q��ƈ使用 XMPP 来充分��用服务器和�Q何相��x��务所提供的功能。同时连接到服务器的可能有多�U�资源，它们代表各自已获授权的客��h��。对于客��h��和服务器之间的连接，推荐使用的端口号�?5222 。网��x��一�U�有着�Ҏ��用途的服务器端服务�Q�它的主要功能是在异构通讯�pȝ��协议之中解析 XMPP �Q�同时还要在 XMPP 之中解析�q�回的数据，如以下各各种服务的网养I��电子邮�g、国际互联网中��聊天�Q�IRC�Q�、SIMPLE、短信息服务�Q�SMS�Q�和现存的各�U�即旉��讯服务�Q�包�?AIM、ICQ、MSN Messenger �?Yahoo! Instant Messenger �{��?br />　　两个基本概念 �?XML 数据��和 XML 节��得较��结构化信息的有效负载可以在敏感于数据传输的实体间进行迅速的异步传输。一�?XML 数据��就像一�U�容器，可应用在��M��两个�|�络实体�?XML 数据元的交换。XML 节是�l�构化信息的独立单元�Q�通过 XML 数据��从一个实体发送到另一个实体�?br />　　XMPP 中包含了一�U�用于防范数据流被窜改和偷听的办法。这�U�信道加密的办法使用了传输层安全协议�Q�TLS�Q�，�q�同其扩展协�?STARTTLS 。这�U�扩展与其它协议的扩展是同一模式的，�?IMAP、POP3 �?ACAP �{�协议。XMPP 中还包含一�U�对数据��进行验证的办法�Q��ƈ采用了简单验证和安全层协议（SASL�Q�中 XMPP 的特定框架�?

协议�l�构
　　XML 数据��在所�?XML 节的传送会话过�E�中起到一�U�包�l�的作用。我们可以采用一�U�单�U�的方式来表�C��个过�E�：
|--------------------|
|            |
|--------------------|
|          |
|             |
|         |
|--------------------|
| |
| |
| |
|--------------------|
| |
| |
| |
|--------------------|
| ... |
|--------------------|
| |
|--------------------|

飛雪(leo) 2006-12-31 13:17 发表评论

开攄��XMPP

飛雪(leo) — Sun, 31 Dec 2006 05:08:00 GMT

��Z��RFC 3920�Q�RFC 2779�{�标准协议的研究�Q�一点个��Z��?

��Z��XMPP的统一消息模型

好久没写文章了，感觉有点累，�l�于�Q�看��C��UU在招人，竟然要求最好是BLOG作�ؓ��历，所以�ؓ之一触，补一下自��q��blog�?/p>

规划了很久的�l�一消息模型�Q�终于在一个图上表现完了：�Q�。。�?/p>

��Z��l�一各个�pȝ��中的消息�Q�计划采用以XMPP协议为基��的统一消息�pȝ��Q�在�pȝ��上构��Z��axis为基��的web service来提供相关的接口标准�Q�这栯��实现吗？

能统一什么？

·�l�一各个�pȝ��的消�?/p>

·�l�一邮�g

·�l�一的短�?/p>

·�l�一的VOIP呼叫

·�l�一��Z��T.38协议的网�l�传�?/p>

·�l�一一切该�l�一�?/p>

支持什么操作系�l�？

Linux、Windows

支持的数据库�Q?/strong>

DB2、ORACLE、MS SQL 、MY SQL、HSQL

能与什么系�l�统一能？

·��Z��WEB的应用系�l�（ASP、PHP、JSP�Q?/p>
·��L��开发语�a��~�写的应用系�l�（C、VB、DELPHI....�Q?/p>

��Z��开攄��axis作�ؓweb service可以很方便的为其他系�l�提供统一的标准及接口�Q�但是会面��一个问题：别�h的系�l��ؓ什么要和你�l�一��h��呢？�q�个问题要思�?...

OA、ERP、CMS�{�都面�͘q�个问题�Q�统一的消息机制是他们急需的，而对于企业，各个�pȝ��中消息的�l�一�Q�以及完善的通知手段�Q�包括文字、邮件、短信、传真、电话等�Q�是必须的�?/p>
使用VoIP相关功能�Q�我们可以徏立多�U�应用服务，例如VoIP+TTS构�g自动语音留言、VoIP多方电话会议�{��?/p>

飛雪(leo) 2006-12-31 13:08 发表评论

RFC 3920 �?XMPP

飛雪(leo) — Sun, 31 Dec 2006 05:05:00 GMT

1 �?/font> Extensible Messaging and Presence Protocol (XMPP): Core

1.1. Status of this Memo/ 说明

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

本文档详�l�说明了应用�?/font> Internet 通讯的标准协议。对于本协议的更新的一些需求讨论和��Q�请提交当前版本到“国际标准协议组�l�”。本文档分发不受限制�?/span>

1.2. Copyright Notice/ 版权��x��

Copyright (C) The Internet Society (2004).

1.3. Abstract/ 概要

This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779.

本文定义�?/font> XMPP 协议的核心特性�?/font> XMPP 是基�?/font> XML ��元素扩展的�Q�它旨在向两个网�l�终端在�q�乎实时的情况下交换�l�构信息�?/font> XMPP 也提供了一个没有显著特点的�Q�可扩展�?/font> XML 数据交换的框架结构模型。在 RFC 2779 标准定义的需求下�Q�它应用于徏立即旉��讯和即时会议的应用�E�序�?/span>

1.4. Table of Contents/ 目录

1.       Introduction/ ��?/font>

2.       Generalized Architecture/ 通用的结�?/span>

3.       Addressing Scheme/ 地址配置

4.       XML Streams/ XML ��?/font>

5.       Use of TLS/ TSL 的应�?/font>

6.       Use of SASL / SASL 的应�?/font>

7.       Resource Binding / 资源�l�定

8.       Server Dialback / 服务回叫

9.       XML Stanzas / XML �?/font>

10.    Server Rules for Handling XML Stanzas / XML 操作的服务规�?/font>

11.    XML Usage within XMPP / XMPP �?/font> XML 用法

12.    Core Compliance Requirements /   核心需�?/span>

13.    Internationalization Considerations / 国际化考虑

14.    Security Considerations / 安全考虑

15.    IANA Considerations / IANA 考虑

16.    References / 参考文�?/span>

17.    Nodeprep / 节点命名

·         B. Resourceprep / 资源命名

·         C. XML Schemas / XML 计划

·         D. Differences Between Core Jabber Protocols and XMPP / JABBER �?/font> XMPP 核心协议的区�?/span>

       ·         Contributors/ 贡献�?/span>

·         Acknowledgements/ 知识准备

·         Author's Address/ 作者地址

·         Full Copyright Statement/ 版权��x��              待箋.........

1.4   1. Introduction/��?/font>

1.4 1.1 Overview/�l�D��

The Extensible Messaging and Presence Protocol (XMPP) is an open Extensible Markup Language [XML] protocol for near-real-time messaging, presence, and request-response services. The basic syntax and semantics were developed originally within the Jabber open-source community, mainly in 1999. In 2002, the XMPP WG was chartered with developing an adaptation of the Jabber protocol that would be suitable as an IETF instant messaging (IM) and presence technology. As a result of work by the XMPP WG, the current memo defines the core features of XMPP 1.0; the extensions required to provide the instant messaging and presence functionality defined in RFC 2779 [IMP-REQS] are specified in the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence [XMPP-IM].

xmpp是一个开攄��Z��xml�?提供 �q�乎实时消息、现场勘察和��h��应答服务的协议。它最初是由jabber开源社区在大约 1999�q�发起�ƈ一直领导的��x��消息的实时系�l�，�?002�q�_��xmpp WG 。作为xmppWG的工作结果，当前备忘录定义了xmpp1.0的核心特�?�?�q�个扩展部要求提供定义在<>的即时消息和现场勘察功能�Q�是列在xmpp �? [xmpp-im]�?/font>

1.4 1.2 Terminology/术语

The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [TERMS].

下面大写的关键字 "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "REC OMMENDED", "MAY", and "OPTIONAL" 在这��文档中的意�?请参见RFC 2119

1.4 2. Generalized Architecture/通用的结�?/font>

1.4 2.1 Overview/�l�D��

Although XMPP is not wedded to any specific network architecture, to date it usually has been implemented via a client-server architecture wherein a client utilizing XMPP accesses a server over a [TCP] connection, and servers also communicate with each other over TCP connections.

The following diagram provides a high-level overview of this architecture (where "-" represents communications that use XMPP and "=" represents communications that use any other protocol).

C1---S1---S2--C3

|

C2---+---G1==============FN1==================FC1

The symbols are as follows:

·C1, C2, C3 = XMPP clients

·S1, S2 = XMPP servers

·G1 = A gateway that translates between XMPP and the protocol(s)

             used on a foreign (non-XMPP) messaging network

·FN1 = A foreign messaging network

·FC1 = A client on a foreign messaging network

��管xmpp不想与�Q何特�D�的�|�络体系机构相结合，但它通常是基于c/s架构的，其中一个客��L��通过一个tcp�q�接按着 xmpp 讉K��一个服务器�Q?服务器同样也�?通过tcp与其它实体通信�?/p>
下面的图表提供了�q�个体系机构的高层视�?--代表用xmpp�q�行通信�Q?代表�?其它协议�q�行通信 )�?

C1---S1---S2--C3

|

C2---+---G1==============FN1==================FC1

·C1,C2,C3 代表 XMPP客户�?/p>
·S1,S2代表XMPP服务�?/p>
·G1代表一个网养I��它XMPP�?其它外部(非xmpp)消息�|�络之间的翻译�?/p>
·FN1 代表一个外部消息网�l?/p>
·FC1 代表一个外部消息网�l�的客户端。                               �?待箋.........

1.4 2.2. Server/服务�?/h3>
A server acts as an intelligent abstraction layer for XMPP communications. Its primary responsibilities are:

·to manage connections from or sessions for other entities, in the form of XML streams (Section 4) to and from authorized clients, servers, and other entities

·to route appropriately-addressed XML stanzas (Section 9) among such entities over XML streams

Most XMPP-compliant servers also assume responsibility for the storage of data that is used by clients (e.g., contact lists for users of XMPP-based instant messaging and presence applications); in this case, the XML data is processed directly by the server itself on behalf of the client and is not routed to another entity.

一个服务担当一个XMPP通信的智能提取层�Q�这主要负责�Q?/p>
·��理一个来自其它通信实体的以xml��方式的�q�接或会话，它可以来自于授权的客��L��、服务器、或者其它通信实体

·路由在基于xml��实体中��h��正确地址的xml�? �W�九�?

大多数的支持xmpp的服务器也可能�ؓ用户担�Q数据存储的职�? 如用��L��联系列表);既然�q�样�Q�服务器代表用户直接处理xml数据�Q�而不被�\由到另一个实体�?/p>

1.4 2.3 Client/客户�?/h3>
Most clients connect directly to a server over a [TCP] connection and use XMPP to take full advantage of the functionality provided by a server and any associated services. Multiple resources (e.g., devices or locations) MAY connect simultaneously to a server on behalf of each authorized client, with each resource differentiated by the resource identifier of an XMPP address (e.g., vs. ) as defined under Addressing Scheme (Section 3). The RECOMMENDED port for connections between a client and a server is 5222, as registered with the IANA (see Port Numbers (Section 15.9)).

大多数的客户端直接通过tcp与服务器�q�接�Q�用XMPP协议充分利用一个服务和��M��相关的服务提供的功能。多个的资源(如设备或地区)可能同时�q�接��C��个服务器�Q�各自代表的一个授权的客户�Q�它们通过XMPP地址(�?<node@domain/home> �?<node@domain/work>)�?strong>resource标识�W�来区别。推荐的�q�接端口�?font color="#ff0000">5222, 它已向IANA注册�?/font>

1.4 2.4 Gateway/�|�关

A gateway is a special-purpose server-side service whose primary function is to translate XMPP into the protocol used by a foreign (non-XMPP) messaging system, as well as to translate the return data back into XMPP. Examples are gateways to email (see [SMTP]), Internet Relay Chat (see [IRC]), SIMPLE (see [SIMPLE]), Short Message Service (SMS), and legacy instant messaging services such as AIM, ICQ, MSN Messenger, and Yahoo! Instant Messenger. Communications between gateways and servers, and between gateways and the foreign messaging system, are not defined in this document.

一个网��x��服务器上的一个具有特�D�目的的服务。它主要的功能是与外部消息系�l�通信�Ӟ��xmpp数据��译成该�pȝ��的协议数据，同是��该�pȝ��q�回的数据翻译成xmpp数据。例如email, irc, SIMPLE,SMS, 和其它的��x��消息�?AIM,ICQ, MSN Messenger, Yahoo!.�|�关与服务器之间的通信 �?�|�关与外部消息系�l�之�?的通信的定义不在这��文档中�?/p>

1.4 2.5 Network/�|�络

Because each server is identified by a network address and because server-to-server communications are a straightforward extension of the client-to-server protocol, in practice, the system consists of a network of servers that inter-communicate. Thus, for example, < juliet@example.com > is able to exchange messages, presence, and other information with < romeo@example.net >. This pattern is familiar from messaging protocols (such as [SMTP]) that make use of network addressing standards. Communications between any two servers are OPTIONAL. If enabled, such communications SHOULD occur over XML streams that are bound to [TCP] connections. The RECOMMENDED port for connections between servers is 5269, as registered with the IANA (see Port Numbers (Section 15.9)).

因�ؓ每一个服务器都可以通过一个网�l�地址来标识，同时因�ؓ服务器之间的通信是客��L��与服务器之间的通信协议的一个直接的扩展�Q�在实践中，�pȝ��׃��互通信的服务器�|�络�l�成。因此，例如< juliet@example.com >能够�?lt; romeo@example.net > 交换消息、现场勘察和其它信息。这�U�模式在使用�|�络地址标准的消息通信协议 (如SMTP)中是常见的，��M��两个通信是可选的。如开启，那么通信在基于xml��上发生�Q�它一定要建立TCP�q�接。推荐的�q�接端口�?font color="#ff0000">5269, 它已向IANA注册�?/font>

1.4 3. Addressing Scheme/地址配置

1.4 3.1 Overview/�l�D��

An entity is anything that can be considered a network endpoint (i.e., an ID on the network) and that can communicate using XMPP. All such entities are uniquely addressable in a form that is consistent with RFC 2396 [URI]. For historical reasons, the address of an XMPP entity is called a Jabber Identifier or JID. A valid JID contains a set of ordered elements formed of a domain identifier, node identifier, and resource identifier.

The syntax for a JID is defined below using the Augmented Backus-Naur Form as defined in [ABNF]. (The IPv4address and IPv6address rules are defined in Appendix B of [IPv6]; the allowable character sequences that conform to the node rule are defined by the Nodeprep profile of [STRINGPREP] as documented in Appendix A of this memo; the allowable character sequences that conform to the resource rule are defined by the Resourceprep profile of [STRINGPREP] as documented in Appendix B of this memo; and the sub-domain rule makes reference to the concept of an internationalized domain label as described in [IDNA].)

jid = [ node "@" ] domain [ "/" resource ] domain = fqdn / address-literal fqdn = (sub-domain 1*("." sub-domain)) sub-domain = (internationalized domain label) address-literal = IPv4address / IPv6address

All JIDs are based on the foregoing structure. The most common use of this structure is to identify an instant messaging user, the server to which the user connects, and the user's connected resource (e.g., a specific client) in the form of . However, node types other than clients are possible; for example, a specific chat room offered by a multi-user chat service could be addressed as (where "room" is the name of the chat room and "service" is the hostname of the multi-user chat service) and a specific occupant of such a room could be addressed as (where "nick" is the occupant's room nickname). Many other JID types are possible (e.g., could be a server-side script or service).

Each allowable portion of a JID (node identifier, domain identifier, and resource identifier) MUST NOT be more than 1023 bytes in length, resulting in a maximum total size (including the '@' and '/' separators) of 3071 bytes.

一个实体可以是��M��|�络端点(如网�l�中的一个ID)�q�能够用XMPP通信的事物�?所有这一�cȝ��实体可以唯一�~�址的，�q�符合[RFC 2396 [URI]]风格�?因�ؓ历史原因�Q?strong>一个XMPP实体的地址被叫做Jabber标识�W�或JID。一个有效的JID包括三个部分�Q?strong>域标识符�Q?strong>节点标识�W?/strong>�?strong>资源标识�W?/strong>

JID语法使用[ABNF]表达式定义�?IPv4地址和IPv6地址的规则的定义在附录B [IPv6] �?/p>

jid = [ node "@" ] domain [ "/" resource ]

domain = fqdn / address-literal

fqdn = (sub-domain 1*("." sub-domain))

sub-domain = (internationalized domain label)

address-literal = IPv4address / IPv6address

所有的JID都是��Z��上述�l�构中的。这个结构大多是用来标识一个即时消息通信的用��P��在服务器上有哪几个连接，及用��L��q�接资源�?lt;user@host/resource> 的�Ş�? 可是,节点的类型可能不是客��L��;例如一个聊天室提供多用戯��天服务，它的地址可以可以�?lt;room@service>( “room”是聊天室的名字�Q?service"是提供多用户聊天服务的主机名) 。或者一个聊天室中的某个用户被编址�?lt;room@service/nick> ( "mick"是该用户在聊天室中的�늧�). ��h��多个其它JID�c�d��是可能的(�?lt;domain/resource>可以是一个服务器端的 script或服�?�?/p>

一个JID的每一部分(域标识符�Q�节�Ҏ��识符和资源标识符)的长度都不能��过1023 个字节，从而��d��节数(包括"@"�?/")不能��过3071个字节�?/p>

待箋......

飛雪(leo) 2006-12-31 13:05 发表评论

XMPP 协议

飛雪(leo) — Sun, 31 Dec 2006 04:54:00 GMT

XMPP 协议

XMPP 协议是在www.jabber.org上公布的�Q�是一�U�标准的��x��通讯协议

JEP-0078

JEP-0078: Non-SASL Authentication

SASL�Q?/span>Simple Authentication and Security Layer ��单的认证及加密层

1、客��L��向服务器端发�?/span>XML��?/span>

xmlns='jabber:client'

xmlns:stream='http://etherx.jabber.org/streams'>

2、服务器�q�回消息

注意中间�?/span>ID�Q�这�?/span>ID是服务器端返回给客户端的验证信息�Q�验证信息一般是以该ID�?/span>+用户密码通过SHA1(RFC3174)��法�q�行操作的。也��是说客��L��得到�?/span>ID和密码经�q?/span>SHA1��法加密后返回给服务器�?/span>

3、客��L��x��务器提交��h��获取��d��需要验证的字段

4、服务器�q�回��d��需要验证的字段

�q�个digest��是上面�l�过SHA1��法得出的结果字�D?/span>

如果客户端发送的字段包括了用户名�?/span>IQ-GET的字�D�，服务器不应该�q�回错误消息�Q�因为需要服务器判断当前用户名是否在使用�Q�，如果服务器不支持可插入的��单认证及密码模块�Q�那么必��返回一�?/strong>的错�?/span>;如果客户端企图��?/span>SASL认证但是��p�|�Q�服务器必须�q�回错误信息

在认证过�E�中�Q?/span>jabber:iq:auth命名、用户名和资源是必须要求客户端提供的�Q?/span>而服务器�q�回�?/span>XML��中也必��L��?/span>�?/span>�q?/span>2个元素�?/span>

5、客��L��提交字段内容�q�行验证

文本格式�Q�非加密模式

bill

Calli0pe

globe

加密模式

bill

48fc78be9ec8f86d8ce1c39c320c97c21d62334d

globe

6、登录结�?/span>

成功

��p�| �?认证��p�|�Q�可能是用户名密码不匚w��或数字验证错�?/span>

��p�| �?资源冲突/错误

��p�| �?没有提供需要验证的字段

其他的就没什么重要的了，JEP-0078��到此了吧，剩余的重要工作就是如何配�|?/span>SASL

飛雪(leo) 2006-12-31 12:54 发表评论

飛雪(leo) — Sun, 31 Dec 2006 04:50:00 GMT

摘要: ��Z��XMPP的JABBERD功能�Ҏ��分�? ... 阅读全文

飛雪(leo) 2006-12-31 12:50 发表评论

91免费精品国自产拍在线不卡,久久亚洲精品中文字幕,日本在线三级

XMPP初解

开攄���XMPP

��Z��RFC 3920�Q�RFC 2779�{�标准协议的研究�Q�一点个��Z���?

RFC 3920 �?XMPP

1 �?/font> Extensible Messaging and Presence Protocol (XMPP): Core

1.1. Status of this Memo/ 说明

1.2. Copyright Notice/ 版权��x��

1.3. Abstract/ 概要

1.4. Table of Contents/ 目录

1.4 1. Introduction/����?/font>

1.4 1.1 Overview/�l�D��

1.4 1.2 Terminology/术语

1.4 2. Generalized Architecture/通用的结�?/font>

1.4 2.1 Overview/�l�D��

1.4 2.4 Gateway/�|�关

1.4 2.5 Network/�|�络

1.4 3.1 Overview/�l�D��

XMPP 协议

XMPP 协议

开攄��XMPP

��Z��RFC 3920�Q�RFC 2779�{�标准协议的研究�Q�一点个��Z��?

1.4 1. Introduction/��?/font>