Ⅰ 如何用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論壇、網吧等網路經營機構的會員溝通。