Ⅰ 如何用java开发基于jabber的IM软件
Jabber对于即时消息是一个开放的、基于XML的数据模型和协议。联系不断增加的基于Jabber开放资源和商业产品的数目，这种协议提供了摆脱即时消息服务器所有权束缚的一种方法。多种多样的开放资源Java APIs能够帮助你建立基于Jabber的服务器并将即时消息整合到你的应用程序中去。在这篇文章中专门阐述了这一点。
即时消息作为个人——个人通迅工具取得了显著的成功。在有些地方它已经作为在线联系的首选方法取代了email。现在，开发者正将这一技术应用到应用程序——个人和应用程序——应用程序通迅上。
直到最近，也只有少数服务提供商掌握了这一技术。通常流行的即时消息服务是建立在所有权协议基础上的通迅孤岛。实施面临一个困难的决策：支持多协议或锁定到一个单独的。不管哪种选择，实现都必须依赖一个属于即时消息（IM）服务提供商的服务器。
开放式协议能够帮助开发者摆脱所有权陷阱。其优势有多种：开放协议鼓励竞争实现的发展（一些开放资源）。他们鼓励广泛采用一种公共协议，这样可以阻止通迅孤岛和服务供应的孤立主义方法的发展。用多种方法，开放协议使因特网成为可能。在即时消息领域，开放协议确保封闭系统及协议不会阻碍基于IM服务器的发展的互操作性。
Jabber是一种针对即时消息和现场服务的开放协议。作为一个公共协议的最主要的侯选者，Jabber有潜力打破所有权在即时消息服务的控制。
这篇文章将解释如何实践发送简单Jabber消息和开发一个简单的基于开放标准及开放资源APIs和产品的布告服务器。
为什么使用Jabber?
Jabber标准和结构帮助创建一个分布式的IM系统，使人联想到分布在因特网上的email系统，用户在本地连接到这些系统。这个方法直接与象AIM（AOL即时信使）、ICQ、MSN（Microsoft网络）及Yahoo这样的流行服务提供商提供的单一系统结构作对，在那里一个单独的中央服务器或集中服务器组提供消息服务。Jabber在其他情形也类似于email结构：Jabber使用一个几乎与基本SMTP（简单邮件传输协议）方案一样的地址方案确定它的终点（人，机器，软件）地址。例如，[email protected]是一个有效的Jabber地址，或使用Jabber说法叫JID（Jabber ID）。因为这些原因，基于Jabber的系统衡量起来好于已存在的专有系统。加之，对于专有即时消息服务的网关允许的协议是必需的。
多种多样的Jabber服务器，包括我们在这篇文章中使用的其中之一，都是自由可使用的，意思就是说你不再需要依赖一个第三方IM服务提供商（第三方Jabber服务对于那些要求第三方主机服务的来说也是有用的）。
标准化
当讨论Jabber标准的益处时，我应该提及IETF IM标准的工作。在写这篇文章时，其IMPPWG（即时消息和现场协议工作组）已有多个RFC有效，其中最重要的是：
·RFC 2778:现场和即时消息模型
·RFC 2779:即时消息/现场协议要求
IMPPWG已经起草了一个名叫CPIM（公共现场和即时消息）协议的因特网标准。Jabber协议也是一个草拟的因特网标准，但不是IMPPWG工作的部份。
Jabber在哪儿适合这一标准工作呢？依照Jabber网站，Jabber是“承诺完全支持任何开放实时消息协议，包括IETF协议”。如果当对于这个IETF协议的支持增长时，Jabber打算将自己定位为IETF协议的领导开放资源的平台。到目前为止，IETF的工作更多地主要集中在收集要求上而不是执行。暂时，Jabber仅是一个带有重要开放资源支持的开放即时消息和现场服务协议。结果，它成为开放即时消息事实上的标准。
另一个值得密切注意的竞争对手是Sun微系统的Jxta协议，另一个基于XML针对peer-to-peer(P2P)应用程序开发者的协议。各种各样的Jxta实施在今天已经能够被提供。但是，由于其起源相对较近，Jxta比起Jabber只有很少的牵引力。
下载并安装
要开始使用Jabber，你首先需要下载必要的工具：你需要一个Jabber服务器，一个Jabber客户端，一个帮助管理和隐藏一些复杂socket处理的API，XML语法分析，消息创建等等。
Jabber服务器
为了运行Jabber,你选择的Jabber服务器不能有问题，自从他们都接受了标准Jabber XML及与终端应用程序通迅以释放负荷，其也是标准Jabber XML。Jabberd，最初的Jabber服务器，是开放资源（但不是基于Java），安装配置简单并在多数平台上都有效，包括Unix、Linux、Windows和Mac OS X。JabaServer开放资源方案也值得提及，但现在，这些基于Java的方案仍不如Jabberd成熟。同时，JabaServer安装不怎么简单易懂，因为你必须下载、安装并配置一个第三方数据库，加上创建必需的数据库规划。
对于这篇文章的例子，我选择Jabberd。当二进制及源下载对于jabberd都有效时，我就不在这儿描述怎样建立一个源发布。除非你真想自己编译，可以从jabberd 主页下载二进制发布。在Windows平台上安装是相对容易的。发布是一个.exe程序，按照安装向导一步一步执行。
安装完成后，你无需配置。在Windows2000，不要求配置。只要双击二进制程序就可启动服务器。
用户代理/客户
我决定使用Exos客户端，对于这个方案这是另一个开放资源技术。我尤其喜欢Exos的调试标签，可以允许你正确地查看客户发送和接收的XML。另外你能够作为纯粹的XML键入Jabber消息并将它们发送给服务器。所有这些都证明用Jabber协议和服务器测试的有用性。
Exos的安装简单易懂。下载Exos 压缩文件（我在文章中使用的是0.6版本）。将文件直接解压到你想要安装客户端的目录。在这个版本中，文件是些简单的二进制文件和一个.dll文件。你可以从 Muse 主页下载Muse API。
发送你的第一个Jabber消息
要发送一个Jabber即时消息，你必须初始化Muse Jabber API。通过创建一个JabberContext 类的实例来完成，接下来使用内容作为一个参数到Jabber session factory类的createSession()方法：
1 //初始化Jabber context
2 JabberContext jabberContext = new JabberContext("user", "pass", "localhost");
4 //创建一个Jabber session factory的实例
5 Jabber jabber = new Jabber();
6 //创建新会话
7 JabberSession jabberSession = jabber.createSession(jabberContext);
上面的例子在第2行显示了一个新context的创建。JabberContext存储了指定的用户相关信息（用户名、密码、用户地址）以及稍后要使用context建立session时包含的一个唯一的会话标识。为了阐述意图，我直接使用了username、password和server。
在第5行，一个Jabber session factory被创建，我们在第7行使用它创建了一个新的JabberSession，Muse进入由Jabber服务器提供的服务的主要接口。服务器的主要服务是：
·连接服务： 从Jabber服务器连接和断开
·用户服务： 针对用户鉴定及注册
·现场服务： 接收从其它用户/服务来的及你自己广播的现场信息
·登记表服务： 密友列表或地址薄
·聊天服务： 发送多种类型的消息—组聊、私聊、标题等等
·服务器服务： 获得与由这个Jabber服务器提供的服务相关的信息
·客户服务： 获得关于其他用户的信息，比如用户登录的最后时间
现在我们已经有了一个已经初始化的Jabber session，我们能够用它在我们才创建的JabberSession对象中使用connect()方法去连接到Jabber 服务器：
8 //连接到服务器
9 jabberSession.connect("localhost", 5222);
要连接到一个Jabber服务器，我们指定地址及在指定服务器上的机器端口号。标准来说，缺省Jabber端口是5222。
现在JabberSession已经连接到服务器，我们能够在我们的服务中用login()方法登录：
10 //登录到Jabber服务器
11 jabberSession.getUserService().login();
在第11行，我们使用JabberSession获得一个到UserService的引用，接下来在我们服务中调用login()方法。注意方法自身不指定任何用户信息。当在上面第7行JabberSession被创建时login()从与JabberSession相关的JabberContext中获得这些信息。
现在我们已经成功登录到Jabber服务器，我们能够开始发送和接收消息。下面代码段显示了如何构造一个简单的标题风格的消息：
12 //构造测试消息
13 JabberChatMessage msg = new
14 JabberChatMessage(JabberChatMessage.TYPE_HEADLINE);
15 msg.setSubject("Hello world");
16 msg.setBody("Hello world");
17 msg.setTo("user2@localhost");
在第13行，我们创建了一个JabberChatMessage实例。单个参数指定了我们要求的消息类型：TYPE_HEADLINE。JabberChatMessage类的名字容易引起误解，实际上，它可以用来包含在Jabber协议中定义的消息的任何四种类型—普通、聊天、标题及错误。在第15行，setSubject()和setBody()分别指定主题和内容。最后，setTo()在第17行设置消息接收器的JID。
在封装下，JabberChatMessage将所有这些信息转换成一个内在的DOM（文档对象模型）树，这样当我们已经准备好发送消息给Jabber服务器时能够轻松产生XML。
最后步骤：用sendMessage()方法发送消息：
18 //发送消息
19 jabberSession.sendMessage(msg);
在封装下
依据上面例子所得的事实，Muse API有效地隐藏了与连接管理和XML语法分析有关的所有细节，因此允许你集中精力在手边的任务上：创建一个消息服务。然而，理解一些基础协议交换证明是有用的。让我们关注一下当我们连接到服务器时发生的XML交换，登录，并象上面代码描述的一样发送消息。在下面的XML交换中，被客户接收的消息（我们例子代码）带了RECV前缀，送到服务器的消息带有SEND前缀：
SEND: <?xml version="1.0" encoding="UTF-8" ?>
<stream:stream to="localhost"
xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams">
RECV: <stream:stream from="localhost" id="3D160545">
所有的Jabber交换都发生在一个XML流的上下文。在我们客户与Jabber服务器之间连接的生命期间，两个完全的XML文档在一个时间传输一个片段。上面显示的最初交换允许客户开始发送XML流文档到服务器并且服务器开始发送XML流文档到客户。
下面，一个要求鉴定的信息被发送给服务器：
SEND: <iq xmlns="jabber:client" type='get' id='id_10028'>
<query xmlns="jabber:iq:auth">
<username>user</username>
</query>
</iq>
RECV: <iq xmlns="jabber:client" type='result' id='id_10028'>
<query xmlns="jabber:iq:auth">
<username>user</username>
<password />
<digest/>
<sequence>482</sequence>
<token>3D15E63A</token>
<resource />
</query>
</iq>
在用户鉴定程序前述那段显示了第一次交换。开始，客户向服务器询问哪种鉴定方式对于给定用户是有效的。服务器段用下面的鉴定方法回答：
·Plain 文本：<password />标签
·零知识鉴定：使用<sequence>和<token>标签
·<digest/>：象plain文本，但密码是SHA-1 (安全无序运算法则)-用用户的plain文本密码进行编码
我们实际上使用<digest/>，象下面代码段描述的一样：
SEND: <iq xmlns="jabber:client" type='set' id='id_10030'>
<query xmlns="jabber:iq:auth">
<username>user</username>
<hash></hash>
<resource>Home</resource>
</query>
</iq>
RECV: <iq xmlns="jabber:client" type='result' id='id_10030'></iq>
在这一点，用户连接到服务器并能够开始发送和接收消息：
SEND: <message xmlns="jabber:client" type='headline'
id='id_10032' to='user2@localhost'>
<thread xmlns="jabber:client">id_10033</thread>
<subject xmlns="jabber:client">Hello world</subject>
<body xmlns="jabber:client">Hello world</body>
</message>
上面片段显示了我们发送给接收者user2@localhost的测试标题消息。
你可能已经注意到在前述协议段有一个重复出现元素：ID标签。因为session能够由多个异步会话组成，ID标签匹配查询并响应。
接收消息
自从这篇文章的主要方向是向你显示如何开发一个报警系统，我就很少注意消息接收。然而，为了完整性的利益，我应该讨论在Muse API中处理接收消息的一些有用特性。另外，因为报警服务是被登录到Jabber服务器的用户执行的，你能够适当地期望一些消息接收者试图与发送者通信。
Muse使用一个listener附在session上以接收进入消息的提示。下面代码显示了如何创建一个listener并将其附到session——listener实际上附加到连接上，但自从我们的接口是在session级别并且JabberSession类有一个便利的方法添加一个listener，我们就将其附加到session：
1 jabberSession.addMessageListener(
2 new JabberMessageListener() {
3 public void messageReceived(JabberMessageEvent event) {
4 if (event.getMessageType() == JabberCode.MSG_CHAT ) {
5 JabberChatMessage msg =
6 (JabberChatMessage)event.getMessage();
7 JabberChatMessage reply = new
8 JabberChatMessage(JabberChatMessage.TYPE_HEADLINE);
9 reply.setTo(msg.getFrom());
10 reply.setSubject("Re: "+msg.getSubject());
11 reply.setBody(
12 "I'm just a sender: please send messages to someone else");
13
14 //发送消息
15 jabberSession.sendMessage(reply);
16 }
17 }
18 }
19 );
客户能够添加几个消息listeners，每次一个消息被接收它们都要被调用。典型的，你为要处理的每一个类型的消息添加一个listener。另一个选择：为同一种消息类型但在那些消息中的每一种不同的行为添加多个listeners。然而另一种选择将添加一个要处理所有消息类型的listener。选择依赖于你想完成什么。
在上面的例子中，一个单独的listener被附加。Listener必须是实现JabberMessageListener接口的类的一个实例。这个接口要求一个要被执行的单个方法： void messageReceived(JabberMessageEvent)。当一个消息从服务器被接收时这个方法将被调用。在例子代码中，messageReceived()方法首先检查在第4行接收的消息类型。自从Jabber用户代理使用了MSG_CHAT类型发送消息，就只对这种类型消息才感兴趣。在第5行，Jabber消息从JabberMessageEvent 提取。在第9行通过设置收件人接收消息被用来构成一个给消息发送者的回复并且在第10行拷贝接收消息的主题。一个缺省错误文本被作为消息体在第11行被设置，并且，在第15行，消息使用前面例子同样的方法利用JabberSession对象的sendMessage()方法传输。
试试Jabber
这篇文章提供了一个对于Jabber协议及少量你能够将这一技术应用到你的应用程序中去的开放资源方案的基本介绍。对这个协议有用的应用程序多种多样，并不限于传统P2P感觉的即时消息领域。例如，jogger.jabber.org提供的Jogger，一个允许你通过发送一个消息给Weblog应用程序（blog）就能更新个人网络杂志的有趣服务。Jabber在用户服务应用程序及其它结构的协作类型应用程序同样有很大的影响。
象上面例子所显示的一样，你使用一个API如Muse或JabberBeans在少许几行Java代码中就能够完成即时消息功能。记住我不能掩盖一些Jabber其它重要的特征，如现场服务和登记表管理，这些在使用时都是相关的。另一个重要的特征是Jabber服务器的模块性和可扩展性，它允许一个开发者创建新的服务直接整合进服务器。
http://wiki.jabbercn.org/space/start
Ⅱ 最优秀的即时通讯软件是什么
MSN
Ⅲ 跪求一篇关于即时通讯系统的英文资料
即时通讯系统Instant Messaging System
Instant Messaging (IM) is a form of real-time communication between two or more people based on typed text. The text is conveyed via computers connected over a network such as the Internet.
Overview
Instant messaging (IM) and chat are technologies that create the possibility of real-time text-based communication between two or more participants over the internet or some form of internal network/ intranet. It is important to understand that what separates chat and instant messaging from technologies such as e-mail is the perceived synchronicity of the communication by the user - Chat happens in real-time before your eyes. Some systems allow the sending of messages to people not currently logged on (offline messages), thus removing much of the difference between Instant Messaging and e-mail.
While many IM services have additional features such as: the immediate receipt of acknowledgment or reply, group chatting, conference services (including voice and video), conversation logging and file transfer, those functions are beyond the scope of this article.
IM allows effective and efficient communication, featuring immediate receipt of acknowledgment or reply. In certain cases Instant Messaging involves additional features, which make it even more popular, i.e. to see the other party, e.g. by using web-cams, or to talk directly for free over the Internet.
It is possible to save a conversation for later reference. Instant messages are typically logged in a local message history which closes the gap to the persistent nature of e-mails and facilitates quick exchange of information like URLs or document snippets (which can be unwieldy when communicated via telephone).
History
Instant messaging actually predates the Internet, first appearing on multi-user operating systems like CTSS and Multics[1] in the mid-1960s. Initially, many of these systems, such as CTSS'.SAVED, were used as notification systems for services like printing, but quickly were used to facilitate communication with other users logged in to the same machine. As networks developed, the protocols spread with the networks. Some of these used a peer-to-peer protocol (eg talk, ntalk and ytalk), while others required peers to connect to a server (see talker and IRC). During the Bulletin board system (BBS) phenomenon that peaked ring the 1980s, some systems incorporated chat features which were similar to instant messaging; Freelancin' Roundtable was one prime example.
In the last half of the 1980s and into the early 1990s, the Quantum Link online service for Commodore 64 computers offered user-to-user messages between currently connected customers which they called "On-Line Messages" (or OLM for short). Quantum Link's better known later incarnation, America Online, offers a similar proct under the name "AOL Instant Messages" (AIM). While the Quantum Link service ran on a Commodore 64, using only the Commodore's PETSCII text-graphics, the screen was visually divided up into sections and OLMs would appear as a yellow bar saying "Message From:" and the name of the sender along with the message across the top of whatever the user was already doing, and presented a list of options for responding.[2] As such, it could be considered a sort of GUI, albeit much more primitive than the later Unix, Windows and Macintosh based GUI IM programs. OLMs were what Q-Link called "Plus Services" meaning they charged an extra per-minute fee on top of the monthly Q-Link access costs.
Modern, Internet-wide, GUI-based messaging clients, as they are known today, began to take off in the mid 1990s with ICQ (1996) being the first, followed by AOL Instant Messenger (AOL Instant Messenger, 1997). AOL later acquired Mirabilis, the creators of ICQ. A few years later ICQ (by now owned by AOL) was awarded two patents for instant messaging by the U.S. patent office. Meanwhile, other companies developed their own applications (Excite, MSN, Ubique, and Yahoo), each with its own proprietary protocol and client; users therefore had to run multiple client applications if they wished to use more than one of these networks. In 1998 IBM released IBM Lotus Sametime, a proct based on technology acquired when IBM bought Haifa-based Ubique and Lexington-based Databeam.
In 2000, an open source application and open standards-based protocol called Jabber was launched. Jabber servers could act as gateways to other IM protocols, recing the need to run multiple clients. Multi-protocol clients such as Digsby,Pidgin, Trillian, Adium and Miranda can use any of the popular IM protocols by using additional local libraries for each protocol. IBM Lotus Sametime's November 2007 release added IBM Lotus Sametime Gateway support for XMPP.
Recently, many instant messaging services have begun to offer video conferencing features, Voice Over IP (VoIP) and web conferencing services. Web conferencing services integrate both video conferencing and instant messaging capabilities. Some newer instant messaging companies are offering desktop sharing, IP radio, and IPTV to the voice and video features.
The term "instant messenger" is a service mark of Time Warner[3] and may not be used in software not affiliated with AOL in the United States. For this reason, the instant messaging client formerly known as Gaim or gaim announced in April 2007 that they would be renamed "Pidgin"
Cooperation
Standard free instant messaging applications offer functions like file transfer, contact lists, the ability to have simultaneous conversations etc. These may be all the functions that a small business needs but larger organisations will require more sophisticated applications that can work together. The solution to finding applications capable of this is to use enterprise versions of instant messaging applications. These include titles like Jabber, Lotus Sametime, Microsoft Office Communicator, etc., which are often integrated with other enterprise applications such as workflow systems. These enterprise applications, or Enterprise Application Integration (EAI), are built to certain constraints, namely storing data in a common format.
There have been several attempts to create a unified standard for instant messaging: IETF's SIP (Session Initiation Protocol) and SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions), APEX (Application Exchange), Prim (Presence and Instant Messaging Protocol), the open XML-based XMPP (Extensible Messaging and Presence Protocol), more commonly known as Jabber and OMA's (Open Mobile Alliance) IMPS (Instant Messaging and Presence Service) created specifically for mobile devices.
Most attempts at creating a unified standard for the major IM providers (AOL, Yahoo! and Microsoft) have failed and each continues to use its own proprietary protocol.
However, while discussions at IETF were stalled, Reuters head of collaboration services, David Gurle (the founder of Microsoft's Real Time Communication and Collaboration business), signed the first inter-service provider connectivity agreement on September 2003. This agreement enabled AIM, ICQ and MSN Messenger users to talk with Reuters Messaging counterparts and vice-versa against an access fee. Following this, Microsoft, Yahoo! and AOL came to a deal where Microsoft's Live Communication Server 2005 users would also have the possibility to talk to public instant messaging users. This deal established SIP/SIMPLE as a standard for protocol interoperability and established a connectivity fee for accessing public instant messaging clouds. Separately, on October 13, 2005 Microsoft and Yahoo! announced that by (the Northern Hemisphere) summer of 2006 they would interoperate using SIP/SIMPLE which is followed on December 2005 by the AOL and Google strategic partnership deal where Google Talk users would be able to talk with AIM and ICQ users provided they have an identity at AOL.
There are two ways to combine the many disparate protocols:
One way is to combine the many disparate protocols inside the IM client application.
The other way is to combine the many disparate protocols inside the IM server application. This approach moves the task of communicating to the other services to the server. Clients need not know or care about other IM protocols. For example, LCS 2005 Public IM Connectivity. This approach is popular in Jabber/XMPP servers however the so-called transport projects suffer the same reverse engineering difficulties as any other project involved with closed protocols or formats.
Some approaches, such as that adopted by the Sonork enterprise IM software or the Jabber/XMPP network or Winpopup LAN Messenger, allow organizations to create their own private instant messaging network by enabling them to limit access to the server (often with the IM network entirely behind their firewall) and administer user permissions. Other corporate messaging systems allow registered users to also connect from outside the corporation LAN, by using a secure firewall-friendly HTTPS based protocol. Typically, a dedicated corporate IM server has several advantages such as pre-populated contact lists, integrated authentication, and better security and privacy.
Some networks have made changes to prevent them from being utilized by such multi-network IM clients. For example, Trillian had to release several revisions and patches to allow its users to access the MSN, AOL, and Yahoo! networks, after changes were made to these networks. The major IM providers typically cite the need for formal agreements as well as security concerns as reasons for making these changes.
[edit] Mobile Instant Messaging
Mobile Instant Messaging (MIM) is a presence enabled messaging service that aims to transpose the desktop messaging experience to the usage scenario of being on the move. While several of the core ideas of the desktop experience on one hand apply to a connected mobile device, others do not: Users usually only look at their phone's screen — presence status changes might occur under different circumstances as happens at the desktop, and several functional limits exist based on the fact that the vast majority of mobile communication devices are chosen by their users to fit into the palm of their hand. Some of the form factor and mobility related differences need to be taken into account in order to create a really adequate, powerful and yet convenient mobile experience: radio bandwidth, memory size, availability of media formats, keypad based input, screen output, CPU performance and battery power are core issues that desktop device users and even nomadic users with connected network.
[edit] Friend-to-friend networks
Instant Messaging may be done in a Friend-to-friend network, in which each node connects to the friends on the friendslist. This allows for communication with friends of friends and for the building of chatrooms for instant messages with all friends on that network.
Emotions are often expressed in shorthand. For example; lol. But a movement is currently underway to be more accurate with the emotional expression. Real time reactions such as (chortle) (snort) (guffaw) or (eye-roll) are rapidly taking the place of acronyms.[citation needed]
[edit] Business application
Instant messaging has proven to be similar to personal computers, e-mail, and the WWW, in that its adoption for use as a business communications medium was driven primarily by indivial employees using consumer software at work, rather than by formal mandate or provisioning by corporate information technology departments. Tens of millions of the consumer IM accounts in use are being used for business purposes by employees of companies and other organizations.
In response to the demand for business-grade IM and the need to ensure security and legal compliance, a new type of instant messaging, called "Enterprise Instant Messaging" ("EIM") was created when Lotus Software launched IBM Lotus Sametime in 1998. Microsoft followed suit shortly thereafter with Microsoft Exchange Instant Messaging, later created a new platform called Microsoft Office Live Communications Server, and released Office Communications Server 2007 in October 2007. Both IBM Lotus and Microsoft have introced federation between their EIM systems and some of the public IM networks so that employees may use a single interface to both their internal EIM system and their contacts on AOL, MSN, and Yahoo!. Current leading EIM platforms include IBM Lotus Sametime, Microsoft Office Communications Server, and Jabber XCP. In addition, instry-focused EIM platforms such as IMtrader from Pivot Incorporated, Reuters Messaging, and Bloomberg Messaging provide enhanced IM capabilities to financial services companies.
The adoption of IM across corporate networks outside of the control of IT organizations creates risks and liabilities for companies who do not effectively manage and support IM use. Companies implement specialized IM archiving and security procts and services like those from Secure Computing, Akonix, SurfControl, and ScanSafe to mitigate these risks and provide safe, secure, proctive instant messaging capabilities to their employees.
[edit] Practical Use in Enterprise
The popular embrace of IM technology for sharing information has quickly led to organizations adopting IM solutions for the perceived advantages that can be brought by it. As organizations are becoming more information based (McNurlin & Sprague, 2006, p.499) the need for effective knowledge sharing, team working and collaborative environments amongst employees has become vital, especially within more geographically dispersed teams.
Typically IM conversations tend to have a certain "character", they are often short and only cover one topic. Media-switching and multitasking are common throughout, however IM might also be used between established coworkers and friends for longer, more intermittent conversation. In their report of IM use at the workplace Nardi et al. (2000) identifies the four primary functions of IM which are often cited in other reports, These primary functions are:
Quick Questions and Clarifications
Coordinating and scheling tasks
Coordinating impromptu social meetings
Keeping in touch with friends and family
IM is perhaps best suited to "Quick Questions and Clarifications" as this is the most often mentioned attribute in other reports. A user can "respond rapidly without the overhead of telephone or FTF interaction. For example, IDC reports, "Users see IM as a medium for quick, semi-permanent ‘flashes’ that beg a near-immediate response" (Isaacs et al., 2002). Nardi's second and third observations are enabled in part e to the "Presence Awareness" feature of IM clients in which the user knows who is "available". This is the most relevant for colleagues who share the same physical space as each other and even paves the way for other mediums to take up the task of communication e.g. F2F or Phone. The implication is that viable communication of any sort can in someway be encouraged through IM's "Presence Awareness" feature. (Issacs et al, 2002) supports this view, "IM in business might not be the main tool for of communication, it could just be the meeting point for another type of media e.g. conference calls.
Nardi's third and fourth observations focus on the social use of IM, which have also been widely publicized in other report. That IM is used for keeping in touch with friends and arranging social events has led some employers to believe that it is used primarily for this purpose. According to (Issacs et al, 2002) a market study found that "'Fear of losing employee proctivity’ was the greatest concern of businesses in regards to instant messaging".
The study by (Issacs et al, 2002) goes on to suggest this fear is unfounded as it was found that on average "only 13% of conversations contained personal topics", and "only 6.4% were exclusively personal".
A study published in 2007, in the Journal of Computer Mediated Communication, found that workers who used instant messaging on the job reported less interruption than colleagues who did not.[5] Research showed that instant messaging was often used as a substitute for other, more disruptive forms of communication such as the telephone, e-mail, and face-to-face conversations. They found that the conversations were briefer between co-workers when using instant messaging than with the other forms of communications. Because of its unique setup, instant messaging allows users to control how and when they communicate with their coworkers. This technology gives people the ability to flag their availability or postpone responses to a more convenient time, according to one of the researchers.[6]
[edit] Review of Procts
"IM solutions can typically be catagorised into two types: Enterprise Instant Messaging (EIM) and Consumer Instant Messaging (CIM). Enterprise solutions use an internal IM server, however this isn't always feasible, particularly for smaller businesses with limited budgets. The second option, using a (CIM) provides the advantage of being inexpensive to implement and has little need for investing in new hardware or server software. However, in recent years open source IM clients such as Jabber have emerged that provide free EIM grade solutions. (Wikipedia,. 2008)
Ⅳ android 即时通讯怎么做
一般都是使用一些传输协议,参考如下:
Android现在即时通讯（或者消息推送）有好几个开源项目框架可以实现，可以使用XMPP来实现即时通信。
XMPP（Extensible Messageing and Presence Protocol：可扩展消息与存在协议）是目前主流的四种IM（IM：instant messaging,即时消息）协议之一，其他三种分别为：即时信息和空间协议(IMPP)、空间和即时信息协议(PRIM)、针对即时通讯和空间平衡扩充的进程开始协议SIP(SIMPLE)。
1. XMPP的前身是Jabber，一个开源形式组织产生的网络即时通信协议。XMPP目前被IETF国际标准组织完成了标准化工作。标准化的核心结果分为两部分； 核心的XML流传输协议 基于XML流传输的即时通讯扩展应用 XMPP的核心XML流传输协议的定义使得XMPP能够在一个比以往网络通信协议更规范的平台上。借助于XML易于解析和阅读的特性，使得XMPP的协议能够非常漂亮。 XMPP的即时通讯扩展应用部分是根据IETF在这之前对即时通讯的一个抽象定义的，与其他业已得到广泛使用的即时通讯协议，诸如AIM，QQ等有功能完整，完善等先进性。
2.XMPP中定义了三个角色，客户端，服务器，网关。通信能够在这三者的任意两个之间双向发生。服务器同时承担了客户端信息记录，连接管理和信息的路由功能。网关承担着与异构即时通信系统的互联互通，异构系统可以包括SMS（短信），MSN，ICQ等。基本的网络形式是单客户端通过TCP/IP连接到单服务器，然后在之上传输XML。
Ⅳ ”IM”的全称是什么
IM(internet message)是即时通讯软件的简称!
像QQ,MSN等
即时消息传递，通常称为IM，是一种类似电子邮件的联机通信方式。 顾名思义，主要区别是IM具有即时性。IM需要特殊的软件程序(如MSN、AOL Instant Messenger、Yahoo Messenger等)。使用这些程序，您可以在对话框中输入要说的话，您的朋友几乎可立即看到您输入的内容。您也可以立即看到朋友输入的内容。 使用IM程序进行通信具有一些与使用电子邮件相同的安全和隐私风险，但值得一提的是，有些风险较为独特。
很多人认为即时消息通话如同聊天，但IM与聊天之间稍有差别。IM通常指两个人之间的通话，而聊天通常指与一群人交谈。如果您要了解一些IM安全决窍，请往下读。
使即时消息传递更安全的十大决窍
1.决不要通过IM通信发送敏感的个人信息，例如信用卡卡号、社会保险编号或密码。
2.只与您的联系人列表或好友列表中的人通信。
3.绝不要同意去面见通过IM认识的网友。
4.绝不要接受陌生人发送的文件或下载项。绝不要接受您不了解的人发送的文件。
5.每个IM程序都会为您分配一个名称，与电子邮件地址类似。该名称通常称为昵称。选择一个不会泄漏个人信息的名称。例如，使用 SassySue代替DetroitSue。
6.监控和限制您的孩子使用IM。如果您注册了MSN Premium服务，您可在孩子与其联系人传递即时消息之前，审批她的所有联系人。您每周还会收到关于孩子上网活动的报告。检查MSN Messenger网站上提供的关于MSN Premium服务所含“父母控制”的更多信息。
7.与电子邮件地址一样，请不要联机张贴您的昵称。有些人会查找并利用您的昵称向您发送垃圾IM消息。
8.不要在工作时发送个人或保密即时消息。您的老板可能有权限查看这些消息。
9.多数即时消息程序允许您在启动计算机时自动登录，以方便您在使用该程序时不必每次都输入密码。如果您使用的是公共计算机，请确保您的IM程序未配置为自动登录。
10.警惕如何显示您何时联机何时脱机。IM程序允许您的联系人列表中的联系人可以查看您的联机状态。然而，此功能可使其他人获得更多您不愿意提供的信息。
Ⅵ 如何用java开发基于jabber的IM软件
联系不断增加的基于Jabber开放资源和商业产品的数目，这种协议提供了摆脱即时消息服务器所有权束缚的一种方法。多种多样的开放资源Java APIs能够帮助你建立基于Jabber的服务器并将即时消息整合到你的应用程序中去。在这篇文章中专门阐述了这一点。 即时消息作为个人——个人通迅工具取得了显著的成功。在有些地方它已经作为在线联系的首选方法取代了email。现在，开发者正将这一技术应用到应用程序——个人和应用程序——应用程序通迅上。 直到最近，也只有少数服务提供商掌握了这一技术。通常流行的即时消息服务是建立在所有权协议基础上的通迅孤岛。实施面临一个困难的决策：支持多协议或锁定到一个单独的。不管哪种选择，实现都必须依赖一个属于即时消息（IM）服务提供商的服务器。 开放式协议能够帮助开发者摆脱所有权陷阱。其优势有多种：开放协议鼓励竞争实现的发展（一些开放资源）。他们鼓励广泛采用一种公共协议，这样可以阻止通迅孤岛和服务供应的孤立主义方法的发展。用多种方法，开放协议使因特网成为可能。在即时消息领域，开放协议确保封闭系统及协议不会阻碍基于IM服务器的发展的互操作性。 Jabber是一种针对即时消息和现场服务的开放协议。作为一个公共协议的最主要的侯选者，Jabber有潜力打破所有权在即时消息服务的控制。 这篇文章将解释如何实践发送简单Jabber消息和开发一个简单的基于开放标准及开放资源APIs和产品的布告服务器。 为什么使用Jabber? Jabber标准和结构帮助创建一个分布式的IM系统，使人联想到分布在因特网上的email系统，用户在本地连接到这些系统。这个方法直接与象AIM（AOL即时信使）、ICQ、MSN（Microsoft网络）及Yahoo这样的流行服务提供商提供的单一系统结构作对，在那里一个单独的中央服务器或集中服务器组提供消息服务。Jabber在其他情形也类似于email结构：Jabber使用一个几乎与基本SMTP（简单邮件传输协议）方案一样的地址方案确定它的终点（人，机器，软件）地址。例如，[email protected]是一个有效的Jabber地址，或使用Jabber说法叫JID（Jabber ID）。因为这些原因，基于Jabber的系统衡量起来好于已存在的专有系统。加之，对于专有即时消息服务的网关允许的协议是必需的。 多种多样的Jabber服务器，包括我们在这篇文章中使用的其中之一，都是自由可使用的，意思就是说你不再需要依赖一个第三方IM服务提供商（第三方Jabber服务对于那些要求第三方主机服务的来说也是有用的）。 标准化 当讨论Jabber标准的益处时，我应该提及IETF IM标准的工作。在写这篇文章时，其IMPPWG（即时消息和现场协议工作组）已有多个RFC有效，其中最重要的是： ·RFC 2778:现场和即时消息模型 ·RFC 2779:即时消息/现场协议要求 IMPPWG已经起草了一个名叫CPIM（公共现场和即时消息）协议的因特网标准。Jabber协议也是一个草拟的因特网标准，但不是IMPPWG工作的部份。 Jabber在哪儿适合这一标准工作呢？依照Jabber网站，Jabber是“承诺完全支持任何开放实时消息协议，包括IETF协议”。如果当对于这个IETF协议的支持增长时，Jabber打算将自己定位为IETF协议的领导开放资源的平台。到目前为止，IETF的工作更多地主要集中在收集要求上而不是执行。暂时，Jabber仅是一个带有重要开放资源支持的开放即时消息和现场服务协议。结果，它成为开放即时消息事实上的标准。
Ⅶ 即时通讯软件需要什么开发技术
作为企业级的即时通讯和融合信息系统，UM联信融合信息平台将通讯技术与计算机软件技术相融合，集成了视频、语音、数据业务，将不同网络中的数据相互转化，为企业和政府用户提供了一套工作协同、信息融合的专业平台。
平台集成了包括文本会话、文件传输、短信收发、网络电话、网络传真、网络会议、视频会等多种沟通方式以及最全面的通讯手段，使用户无论何时、何地，均可使用多种设备随时处理不同系统中的消息，可以有效地保证用户促进工作协同，提升沟通效率，降低通讯费用，响应速度大大提升。
在企业的应用中，UM联信体现了以下几大特点：
◆ 即时通讯：强加内部沟通，提升管理软件的即时性，提高办公效率
◆ 统一消息：多系统的统一消息提醒，革命性的将“人找事”转化为“事找人”
◆ 桌面办公：多门户系统多页面的快速通道，单点登录，一站式验证
◆ 更安全更可靠的协议，多方式的多形式的数据加密
◆ 统一通信：带来更多的协作方便性，网络通讯迅速降低沟通成本
◆ 统一管理：可管可控的统一管理计费控制平台
◆ 指挥催办：快速智能的消息分发，数据结果分析统计
◆ 组织结构的统一：方便快速的定位和查找人员，并与之联系协作
◆ 会议沟通：提供多种形式的会议模式，满足不同会议的需求
◆ 网络服务人员随时咨询，解决软件问题，提高顾客的满意度
UM联信是企业信息化的最优选择。
UM联信——即时通讯带来的优势
即时通讯：加强内部沟通，提升管理软件的即时性，提高办公效率
现状分析：目前，企业与政府为了提高办公效率，纷纷上了管理软件（比如：OA）。此类软件一般都是基于工作流来实现办公的，基于B\S结构的，属于分时业务系统。该类系统中的消息，需要工作人员时刻关注，需要时刻开着IE页面并且还需要即时刷新，很是麻烦。如果不在系统相关的页面上，一些重要事情往往无法通知相关人士，而得不到到及时的审批而造成事务越积越多，影响了办公效率。那如何解决这种分时业务，实现即时的提醒，是目前的一大困惑；同时，在工作中往往会遇到要发送一些超大的附件（几十兆）给同事，但内部的邮件系统不能支持超大的文件发送，往往要用U盘传递或者文件局域网共享等办法，较繁锁；而在工作中常常要找同事（不在同一间办公室），问问一些相关的紧急事务，电话沟通但往往占线，无法即时沟通，往往要亲自跑一趟，而这，费力又费时，效率也不高。那如何解决同事之间的即时沟通问题，如何传递超大的文件，这也是摆在我们面前的一大困惑。
解决之道：UM联信的即时通讯平台是面向企业级应用的，基于C\S结构的。在面向工作人员的客户端上可以统一呈现单位所有的人员组织信息，这样就可以快速的找到你要找那个同事，并能迅速发起与他的对话，直接拖拽你想发送的超大文件，对方就能立刻看到你发送的消息，立刻就能提示对方接收你的文件。如果对方不在客户端上，没有关系，对于文本消息，UM联信不仅支持离线留言，还提供短信的直接发送；对于文件传输，UM联信也支持离线文件传输，等接收方上线之后，就能马上收到，保证消息的即时性。
而且UM联信还兼容飞鸽传输，同时兼容外网和局域网两部分，基于XMPP（IETF国际标准组织IM通讯标准）、DNS 集群通讯解析，实现S2S（服务器与服务器之间）的通讯服务器集群应用。解决目前企业即时通讯系统不能互联互通的难题，开拓分众即时通讯互联互通的先河，并提供软件插件库扩展增值应用机制，建立最普及的电子商务即时通讯群。
使用UM联信，需安装联信服务器端，客户端通过登录服务器端来进行通讯，服务器端可进行统一管理。（客户端可与软件“飞鸽传书”兼容）适合于各种集团公司、中小企业、分支机构、经济联盟体，政府机关及关联机构，行政事业等实体组织的协同商务工作和组织间的电子商务通讯。同时可用于各种垂直门户、行业网站、电子商务网站、SNS论坛、网吧等网络经营机构的会员沟通。