Feed aggregator

http://xeus.googlecode.com/files/xim.zip

- some fixes

- improved message rendering

- live preview of the links!

XPath support for my XMPP libraries was on my TODO list for a long time. Because agsXMPP is using its own DOM implementation I wasn’t able to use standard XPath libraries. Writing a custom XPath implementation is quite a challenge, and using System.Xml’s XPath functions would require 2 different DOMs and parsing the Xml twice, which was no option for me.

Because MatriX is using System.Xml.LinQ which has XPath support it was pretty easy to get this task done for MatriX now.

Of course you can do filtering based on powerful LinQ statements and the other filter classes in MatriX. But in many cases it’s required to build expressions dynamically on the fly. Also many programmers are familiar with XPath and prefer XPath over LinQ statements. The XPathFilter makes it also much easier to filter big complex stanzas with many nested elements.

The following example describes the usage of the XPathFilter. We setup a filter that matches all presence stanzas from the full Jid ‘user@jabber.org/MatriX’. Because MatriX and XPath in .Net are namespace aware we have to define prefixes in the XmlNamespaceManager. Otherwise we would get no results.

e.Stanza is the complete stanza which matches the expression.
e.Result is the result of the XPath expression. This is useful when you are interested only in fragments of the complete stanza.

void XPathFilter() { xmppClient.XPathFilter.XmlNamespaceManager.AddNamespace("JC", "jabber:client"); xmppClient.XPathFilter.Add("/JC:presence[@from='user@jabber.org/MatriX']", XPathCallback); } void XPathCallback(object sender, XPathEventArgs e) { Debug.WriteLine("Stanza: " + e.Stanza); Debug.WriteLine("Result: " + e.Result); }

Here are some other XPath example expressions to filter stanzas:

• filter all messages with the exact body of 'Hello MatriX
  /JC:message[JC:body='Hello MatriX']
• filter all presences where the Jid starts with 'gnauck@'.
  /JC:presence[starts-with(@from ,'gnauck@')]
• filter all messages of type=error which have a from and and a to Jid
  /JC:message[@from and @to and @type='error']

Our OneTeam XMPP client for Linux, Mac OS X, and Windows is entering a private alpha period.

OneTeam is a multiplatform XMPP client for Linux, Mac OS X, and Windows. We have slowly worked on it during long months (and even years, it is being developed since 2006) but never had enough time and resources to release it properly.

The time to launch OneTeam in the wild and interoperable internet is soon arriving. We believe we have achieved our goal to deliver some real enterprise-class user experience. As a proof, we are using it inhouse on a daily basis as a productivity tool, without any major glitch.

For the record, OneTeam works as a Firefox extension, as well as a standalone application, on the three major platforms, thanks to the XUL technology. OneTeam has a nice dashboard-based interface, and handy user interactions improvements everywhere. This XMPP client supports a wide range of features, including chat and presence of course, but also Multi-User Chat (groupchat), message threading, history browsing, etc. It also features Jingle voice calls, as well as the exclusive Jingle Nodes feature demoed at FOSDEM, that works much like Skype. On the more technical side, there is the XML console, as well as a very interesting remote debugging console.

So, we are now releasing OneTeam, but in alpha quality for now, to the curious ones, and those willing to help and test. Please feel free to contact us, if you want to join the alpha testing, and report issues. Please e-mail nverite at process-one.net for a OneTeam ride.

I proudly announce that we have the first Jingle based VoIP Application on IPhone that supports Calling Over 3G!
This application is Nimbuzz, a fully featured Client that supports VoIP via Nimbuzz Contacts, NimbuzzOut, Skype, GTalk, Yahoo, MSN and it is also a SIP Client. It is the Mobile VoIP Freedom Gadget.
The battry consumption really rocks if compared with regular SIP Clients, plus the benefit to be able to receive and place calls, through different methods without any extra battery consumption.
The Application is Free on Apple AppStore and it is also available with VoIP support for Symbian, Android and Windows Mobile.

It uses XMPP and Jingle as the main bus for their services, enabling also the usage of your Nimbuzz account through other Clients like Adium, Pidgin, PSI, Empathy, Pandion, etc...

I am pleased to announce a new MatriX releases. All 3 MatriX editions were updated to
1.2.1.0 and are in sync with the version number now.

This release includes also the first version of the MatriX developer guide with many code examples. I will add continuous more content, code snippets and examples to this guide.

Download the new releases from here.

I am happy to announce release of a new version of the Tigase XMPP Server. This is the first version of the 5.x line and the code is still under intensive tests. As most of the tests are already passed and the code runs on a few live installations I consider this to be Beta ready.

Packages are available from the download page. As usually the test page has been updated with automatic tests' results for the published version.

Changelog list is quite long and modifications fall into a few categories:

Protocol:

1. A new implementation for handling external components connections, supporting XEP-0114, XEP-0225, with protocol auto-detection, multiple connections on a single port, multiple connections for a single external domain, etc…..
2. Full support for stringprep added. The use of the full stringprep processor is optional (off by default) and the JID processing can be changed via pluggable framework. 3 processors available now: full stringprep - very resources expensive, simple (regex based) - default, empty - no processing at all.
3. Roster changes: fixed issue with buddy name set to 'null' in some cases , multiple roster elements are now allowed for set requests, stringprep optimisations, support for extended buddy information to be stored with roster data in DB.
4. Fixed a problem with s2s connections for external components connected to the server - they are automatically detected by s2s component and all the traffic is routed properly
5. Fixed problem with not sending stream closing tag in some cases when the connection to the client is closed
6. Fixed rare issue occurring if there are multiple user connections with the same resource that the older connection with the resource was not closed.
7. Number of bug fixes and optimisations in s2s implementation, still no TLS support yet though.
8. Stream compression can be now activated at any time, it is up to the client to decide

Administration:

1. Server configuration code reworked, fixed an old issue with init.properties and tigase.xml configuration files, tigase.xml is no longer used by default (still possible though), configuration can be stored in the database and configuration management available via ad-hoc commands and scripting API.
2. Configurable packet filtering for every component separately can be loaded as plugins (and API)
3. MySQL schema and stored procedures updates for UTF-8 encoding, changed a last_login, last_logout fields default values from 0 to some correct and sensible value.
4. To overcome problems with packets order on some system there is a configuration option to not use priority queues which may sometimes cause packet reordering.

Development:

1. Scripting API reworked, this is not the server built-in core feature and the scripting feature is now available to all components automatically
2. Component repository API - an easy to use framework for tigase component developers to store certain kind of data in database - the data can be also manipulated via ad-hoc commands and scripting
3. Added secure logging mode for XMPP stanzas to prevent privacy issue - XML element CData is replaced with text: 'CDATA size: NNN'
4. A new API for component tasks added - based on Java TimeoutTask but a single thread controls all the component tasks
5. Lots of JavaDoc documentation has been added and online guides on the website
6. All the core Tigase code to use new JID and BareJID classes instead of String
7. Packet API changed to optimise ways stanza to/from addresses (JIDs) are used.
8. New SM plugging processors API introduced and an abstract class which make it very easy to follow packet flow. This is to avoid confusing detection where from, where to the packet is going (from the user, to the user, to the server….)
9. User registration code changed to allow for storing any kind registration data, the user can provide an extended form with additional fields and they all are stored in the DB

read more

Preview 2 with some fixes try here http://xeus.googlecode.com/files/xim2.zip