<?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="2.0" xml:base="http://www.whitemiceconsulting.com">
<channel>
 <title>WhitemiceConsulting.Com - XMPP</title>
 <link>http://www.whitemiceconsulting.com/taxonomy/term/23/0</link>
 <description>The open standard for instant messaging.</description>
 <language>en</language>
<item>
 <title>Jabber-NET 1.0 Release!</title>
 <link>http://www.whitemiceconsulting.com/node/138</link>
 <description>&lt;p&gt;The &lt;a href=&quot;http://code.google.com/p/jabber-net/&quot;&gt;Jabber-Net&lt;/a&gt; project has finally [and rather amazingly if you know the jumbled history of this project] issued a &lt;a href=&quot;http://groups.google.com/group/jabber-net/browse_thread/thread/e247ce827e7d825c?hl=en&quot;&gt;release 1.0 announcement&lt;/a&gt;.  Lots of great new features including DNS SRV as well as GSSAPI support.  License is either GPL or JOSL.&lt;/p&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/12">dot NET</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <pubDate>Sun, 17 Feb 2008 15:19:10 -0500</pubDate>
</item>
<item>
 <title>SASL Failure with jabber-net</title>
 <link>http://www.whitemiceconsulting.com/node/136</link>
 <description>&lt;p&gt;When using the &lt;A HREF=&quot;http://code.google.com/p/jabber-net/&quot;&gt;jabber-net&lt;/A&gt; assembly a SASL failure doesn&#039;t invoke &lt;code&gt;OnAuthError&lt;/code&gt; as one would intuitively expect;  SASL failures invoke the generic &lt;code&gt;OnError&lt;/code&gt; method with a &lt;code&gt;jabber.connection.sasl.SASLException&lt;/code&gt;.  Just an interesting bit of trivia to avoid a potential gotcha.&lt;/p&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/12">dot NET</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <pubDate>Sun, 17 Feb 2008 14:42:02 -0500</pubDate>
</item>
<item>
 <title>Jivin&#039; With JIVE</title>
 <link>http://www.whitemiceconsulting.com/node/96</link>
 <description>&lt;p&gt;In November of 2005 I presented this presentation entitled &quot;Jivin&#039; with JIVE&quot; to the &lt;a href=&quot;http://www.kalamazoolinux.org&quot;&gt;Kalamazoo Linux User Group&lt;/a&gt;.  This presentation covered deploying and configuring the JIVE Messenger (now called &quot;&lt;a href=&quot;http://www.jivesoftware.org/wildfire/&quot;&gt;Wildfire&lt;/a&gt;&quot; service to provide XMPP (instant messaging).&lt;/p&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/21">Wildfire</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <enclosure url="system/files?file=JIVE-2005.pdf" length="1120124" type="application/pdf" />
 <pubDate>Sun, 19 Feb 2006 22:04:26 -0500</pubDate>
</item>
<item>
 <title>XMPP &amp; Wildfire</title>
 <link>http://www.whitemiceconsulting.com/node/83</link>
 <description>&lt;ul&gt;
&lt;li&gt;XMPP&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Links&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.xmpp.org/&quot;&gt;The XMPP Home Page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://www.jabber.org/&quot;&gt;The Jabber Home Page&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;HOWTOs&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/node/74&quot;&gt;XMPP Notification from OpenNMS&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Wildfile
&lt;ul&gt;
&lt;li&gt;Links&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.jivesoftware.org/wildfire/&quot;&gt;The Wildfire Home Page&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;News&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/node/75&quot;&gt;The name change from &quot;JIVE Messenger&quot;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/21">Wildfire</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <pubDate>Sat,  7 Jan 2006 23:40:33 -0500</pubDate>
</item>
<item>
 <title>JIVE Messenger is now &quot;Wildfire&quot;</title>
 <link>http://www.whitemiceconsulting.com/node/75</link>
 <description>&lt;p&gt;The XMPP server &quot;Jive Messenger&quot; is now &quot;&lt;a href=&quot;http://www.jivesoftware.org/wildfire/&quot;&gt;Wildfire&lt;/a&gt;&quot;.  You can read about the name change &lt;a href=&quot;http://www.jivesoftware.org/wildfire/name_change.jsp&quot;&gt;here&lt;/a&gt;, as well as the 33% performance increase achieved through optimization &lt;a href=&quot;http://www.jivesoftware.org/wildfire/article_optimization.jsp&quot;&gt;here&lt;/a&gt;.   Those crazy cats over at &lt;a href=&quot;http://www.jivesoftware.org&quot;&gt;jivesoftware&lt;/a&gt; have also created the &lt;a href=&quot;http://www.jivesoftware.org/community/entry!default.jspa?categoryID=17&amp;amp;externalID=422&quot;&gt;Pampero&lt;/a&gt; project to bring the next level of scalability to the &lt;a href=&quot;http://www.jivesoftware.org/wildfire/&quot;&gt;Wildfire&lt;/a&gt; server.&lt;/p&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/21">Wildfire</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <pubDate>Sat,  7 Jan 2006 23:30:24 -0500</pubDate>
</item>
<item>
 <title>XMPP Notification From OpenNMS</title>
 <link>http://www.whitemiceconsulting.com/node/74</link>
 <description>&lt;p&gt;&lt;a href=&quot;http://www.opennms.org&quot;&gt;OpenNMS&lt;/a&gt; is a sophisticated and feature rich enterprise ready network monitoring solution (NMS).  &lt;a href=&quot;http://www.opennms.org&quot;&gt;OpenNMS&lt;/a&gt; will monitor your systems via SNMP for performance information as well as availability by performing actual service requests such as HTTP requests.  One of the most important features of any NMS is the ability to notify administrators when something has gone wrong either by e-mail, page, or some other means.  &lt;a href=&quot;http://www.opennms.org&quot;&gt;OpenNMS&lt;/a&gt; supports a variety of notification methods (and you can add your own), and since version &lt;a href=&quot;https://sourceforge.net/docman/display_doc.php?docid=27506&amp;amp;group_id=4141#N10190&quot;&gt;1.2.1&lt;/a&gt; this includes &lt;a href=&quot;http://www.xmpp.org/&quot;&gt;XMPP&lt;/a&gt; (aka &quot;&lt;a href=&quot;http://www.jabber.org/&quot;&gt;Jabber&lt;/a&gt;&quot;).&lt;/p&gt;
</description>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/19">OpenNMS</category>
 <category domain="http://www.whitemiceconsulting.com/taxonomy/term/23">XMPP</category>
 <pubDate>Sat,  7 Jan 2006 23:31:03 -0500</pubDate>
</item>
</channel>
</rss>
