If you are interested in the Tigase project and want to participate in any way you can request an account on the website and Jabber server in domain tigase.org. Please use the contact form to request the account and describe your planed involvement in the project. You can report bugs or request new features on the project tracker.
If you are looking for a free, XMPP account offered from the Tigase based service you should check the Tigase.im Website. This is the place where the last development version of the Tigase server is running. Check the website for more details.
For professional services and commercial Tigase products please refer to the company website: www.tigase.com
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.
Changelog list is quite long and modifications fall into a few categories:
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…..
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.
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.
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
Fixed problem with not sending stream closing tag in some cases when the connection to the client is closed
Fixed rare issue occurring if there are multiple user connections with the same resource that the older connection with the resource was not closed.
Number of bug fixes and optimisations in s2s implementation, still no TLS support yet though.
Stream compression can be now activated at any time, it is up to the client to decide
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.
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….)
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
A while ago, I have written an article about Linux settings for high load systems. This is a description for just very basic settings which are essential to successfully run XMPP service for hundred of thousands online users.
Normally you would not call something a load test if there are just 40 user connections opened to the server.
This time, however the Tigase was running on the mobile phone which is itself an interesting achievement. One thing, however is to just run the application and another is to actually make it do something useful.
The Tigase running there was just the standard version you can download from the website, no single line of code was changed. And also the N900 was running all the standard applications as a fully functional mobile phone.
The only change I made to the phone was installation of the JRE and Bash shell, the rest remained unchanged and none of applications running on the phone was stopped.
All the connections to the server were established via mobile network and all the connections were encrypted with TLS.
I am at the XMPP Summit/FOSDEM now. Thanks to people form Nokia we have an opportunity to play and run some software on N900 devices and thanks to Florian from Flosoft we have SIM cards for data transfer.
What is the most tempting thing for the software developer? Well, at least for me is to run my software on any possible device.
Taking the opportunity to use N900 and play with it I just had to try to run Tigase on it. I have already tested Tigase on small computers, Netbooks with ATOMs and small amount of memory. Tigase passes all tests when run with 10MB of memory so I was pretty sure N900 has enough memory and power to run Tigase.