<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://groups.apu.edu/awg">
<channel>
 <title>AWG - Jabber</title>
 <link>http://groups.apu.edu/awg/taxonomy/term/74/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>Lotus Sametime Supports XMPP (Jabber)</title>
 <link>http://groups.apu.edu/awg/node/273</link>
 <description>&lt;p class="MsoNormal"&gt;Lotus had adopted the &lt;a title="Wikipedia SIMPLE Entry" target="_self" href="http://en.wikipedia.org/wiki/SIMPLE"&gt;SIMPLE&lt;/a&gt; protocol early in its branching off from SIP, and it still a work in progress.&amp;nbsp; Now, like many others, Lotus has adopted &lt;a title="Wikipedia XMPP" target="_self" href="http://en.wikipedia.org/wiki/Xmpp"&gt;XMPP&lt;/a&gt;, the protocol behind &lt;a title="Jabber.org Website" target="_self" href="http://www.jabber.org"&gt;Jabber&lt;/a&gt; as well.&amp;nbsp; This means that there is yet another mainstream product that is interoperable with other XMPP-based services, including &lt;a title="APU IM Website" target="_self" href="http://apuim.apu.edu"&gt;APU IM&lt;/a&gt; and &lt;a title="Google Talk Page" target="_self" href="http://www.google.com/talk/"&gt;Google Talk&lt;/a&gt;.&lt;/p&gt;&lt;p class="MsoNormal"&gt;Source:&amp;nbsp; &lt;a href="http://www.eweek.com/article2/0,1759,2068781,00.asp"&gt;http://www.eweek.com/article2/0,1759,2068781,00.asp&lt;/a&gt; &lt;br /&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 07 Dec 2006 08:52:14 -0800</pubDate>
</item>
<item>
 <title>Playing Catchup with Jabber Summer News</title>
 <link>http://groups.apu.edu/awg/node/102</link>
 <description>&lt;p&gt;It appears as though more of the industry is waking up to &lt;a href=""&gt;Presence Being the Killer App&lt;/a&gt;.  With Jabber Inc. being a leader in this space.  &lt;q&gt;Jabber, Inc., which develops real-time communication server platforms for developing IM and presence-enabled applications, is fashioning its XCP platform into an application server of sorts not only for presence, but also for messaging, routing and XML-application development. In September, it will release a publish-and-subscribe technology called Information Broker for pushing content out to users.&lt;/q&gt;

&lt;p&gt;Interesting too, is the increase in adoption of Enterprise IM (EIM) and consequent integration of presence in business applications.  &lt;q&gt;A recent Osterman Research study shows 44% of companies use IM with business applications, up from 21% just three years ago. Furthermore, 34% of users have standardized on an internally run IM platform, up from 24% just two years ago.&lt;/q&gt;

&lt;p&gt;Jabber Inc. is has &lt;a href="http://www.jabber.com/index.cgi?CONTENT_ID=447"&gt;announced new versions&lt;/a&gt; of its commercial Jabber server and client.&lt;/p&gt;</description>
 <pubDate>Tue, 21 Sep 2004 12:17:07 -0700</pubDate>
</item>
<item>
 <title>MUC Support in Psi</title>
 <link>http://groups.apu.edu/awg/node/46</link>
 <description>&lt;p&gt;Was curious as to where the &lt;a href="http://psi.affinix.com/"&gt;Psi Jabber Client&lt;/a&gt; was in implementing the complete XMPP 1.0 protocol now that it has become a proposed standard by the IETF.  The feature that is most lacking in Psi, is Multi User Chat (MUC) or &lt;a href="http://www.jabber.org/jeps/jep-0045.html"&gt;JEP-0045&lt;/a&gt;.  The older Groupchat protocol is supported, but lacking are advanced features such as moderation and creating and maintaining persistent rooms.&lt;/p&gt;

&lt;p&gt;The &lt;a href="http://psi.affinix.com/?page=development"&gt;Psi Development Roadmap&lt;/a&gt; has a definte plan for completing the XMPP 1.0 implementation and MUC support&lt;/p&gt;

&lt;p&gt;There is also a &lt;a href="http://psi.affinix.com/flyspray/index.php?do=details&amp;amp;id=213"&gt;MUC Feature Status Page&lt;/a&gt; where you can monitor progress on this feature.&lt;/p&gt;</description>
 <pubDate>Tue, 13 Jul 2004 14:47:46 -0700</pubDate>
</item>
<item>
 <title>Jabber Inc. enters the mobile wireless market</title>
 <link>http://groups.apu.edu/awg/node/32</link>
 <description>&lt;p&gt;Jabber, Inc. has announced a suite of wireless clients for RIM, PocketPC, Smartphone, Symbian and J2ME devices, as well as gateways for WAP and SMS.&lt;/p&gt;

&lt;p&gt;Apparently they are currently available for testing, but will be released April 1st.&lt;/p&gt;
                                     
&lt;p&gt;See the &lt;a href="http://www.jabber.com/index.cgi?CONTENT_ID=408"&gt;Press Release&lt;/a&gt;.&lt;/p&gt;</description>
 <pubDate>Thu, 04 Mar 2004 16:19:08 -0800</pubDate>
</item>
<item>
 <title>Jabber Inc. Releases XCP 3.0</title>
 <link>http://groups.apu.edu/awg/node/29</link>
 <description>&lt;p&gt;Jabber has &lt;a href="http://www.jabber.com/index.cgi?CONTENT_ID=407"&gt;announced&lt;/a&gt; the availability of a new major release of their eXtensible Communcations Platform, XCP 3.0.&lt;/p&gt;

&lt;p&gt;New Features&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;improved hooks for standard SNMP (Simple Network Management Protocol) monitoring&lt;/li&gt;
&lt;li&gt;support for SASL (Simple Authentication and Security Layer)&lt;/li&gt;
&lt;li&gt;internationalization features that make XCP ready for localization out-of-the-box&lt;/li&gt;
&lt;li&gt;a graphical controller for configuring the Jabber XCP server&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The story was announced yesterday, but I still don't see the files available on our support page.  So I can't read the more detailed release notes.  I am curious as to how much of the &lt;a href="http://www.jabber.org/ietf/draft-ietf-xmpp-core-22.html"&gt;XMPP Core&lt;/a&gt; and &lt;a href="http://www.jabber.org/ietf/draft-ietf-xmpp-im-21.html"&gt;XMPP IM&lt;/a&gt; IETF Proposed Standards they comply with.&lt;/p&gt;</description>
 <pubDate>Thu, 04 Mar 2004 14:49:45 -0800</pubDate>
</item>
</channel>
</rss>
