Wildfire 3.1.0 review
DownloadWildfire is a leading Open Source, cross-platform IM server based on the XMPP (Jabber) protocol. Wildfire server has great perform
|
|
Wildfire is a leading Open Source, cross-platform IM server based on the XMPP (Jabber) protocol.
Wildfire server has great performance, is easy to setup and use, and delivers an innovative feature set.
Wildfire is an enterprise instant messaging (EIM) server dual-licensed under the Open Source GPL and commercially. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber).
Wildfire is incredibly easy to setup and adminster, but offers rock-solid security and performance.
Use Wildfire in your organization as a more secure and feature-rich alternative to the consumer IM networks. Or, replace your existing EIM server with a more open, easier to use, and much less expensive solution.
Enterprise Grade
Wildfire supports SSL/TLS encrypted connections out of the box as well as packet auditing to meet compliance requirements. Optionally tie Wildfire into your organization's existing authentication system such as LDAP and then handle thousands of concurrent users on a single server.
Open Source and Open Protocol
Wildfire is available under the Open Source GPL or a commercial license. It supports the open XMPP (Jabber) IM protocol and popular extensions. XMPP is supported by dozens of IM clients and allows for easy federation between IM servers. Wildfire is among the most compliant XMPP servers available.
Cross-Platform
As a 100% Java application, Wildfire supports Windows, Unix/Linux, and Mac OSX. The server can be deployed as a standalone application or service, or deployed in any J2EE compliant application server (Tomcat, Resin, etc) as a WAR (Web Application Archive).
Easy to Use
Get Wildfire up and running within ten minutes. Then, administer the server using the web-based admin console.
Plugins
The server is easily extensible with a full plugin architecture. Visit the plugin library for a full list of available plugins.
Spark IM Client
Wildfire works great with the cross-platform, feature-rich Spark IM client. Use the Spark Manager server plugin to manage the Spark clients on your server.
Server-Managed Contact Lists
Define groups of users in the server and then use the shared-group feature to automatically push those groups into user's contact lists. This makes it very easy for people to start using the system and find the people they work with.
What's New in This Release:
Wildfire New Features
[JM-761] - Added new gateway plugin with AIM and ICQ support. (36 votes)
[JM-769] - Added Yahoo protocol support to the gateway plugin. (18 votes)
[JM-770] - Added MSN protocol support to the gateway plugin. (27 votes)
[JM-193] - Improved LDAP support. (26 votes)
[JM-820] - Added support for presence event listeners.
[JM-797] - Added database statistics monitoring.
[JM-807] - Added support for roster event listeners.
[JM-804] - Added support for component event listeners.
[JM-860] - Added Pack200 support for plugins.
[JM-843] - Optimized session retrieval from SessionManager.
[JM-816] - Created ad-hoc commands for managing groups.
[JM-808] - Enhanced roster to be able to hold non-persistent roster items.
[JM-194] - Editing of users is now not allowed when they are read-only. (1 vote)
[JM-833] - Improved wildfired script.
[JM-771] - Added search method to GroupProvider. (1 vote)
[JM-824] - Added #getComponents() to InternalComponentManager.
[JM-827] - Upgraded to hsqldb 1.8.0.5.
[JM-805] - Updated JVM to 1.5.0_08.
Wildfire Bug Fixes
[JM-851] - Fixed presence issues with LDAP and shared groups. (3 votes)
[JM-844] - Enabled LDAP connection pooling by default.
[JM-832] - Connection pooling is no longer used for LDAP authentication.
[JM-846] - Improved error handling if connection to JS plugin update service is not possible.
[JM-854] - Improved handling of SQL command parts.
[JM-839] - Internal server errors while processing MUC packet was not returning any response to client.
[JM-842] - Message flooding was checking ALL sessions instead of only user sessions.
[JM-818] - Change in DB upgrade code broke plugin upgrades.
[JM-819] - Upgrades for non-Wildfire schemas was checking against wrong version.
[JM-822] - Users from LDAP now have correct creation date.
[JM-691] - Documentation for "Create a shared roster group" was incorrect. (3 votes)
[JM-826] - MUC disco name was being hardcoded.
[JM-828] - Rooms were allowing owners, admins and outcasts to be duplicated.
[JM-862] - Messages with no body and no subject were being logged in group chat rooms.
[JM-817] - Fixed small security hole in email settings page.
[JM-781] - Stream compression is now optional by default for client-2-server connections.
[JM-792] - Improved syntax of LDAP searchFilter and groupSearchFilter.
[JM-809] - In band registration was accepting new users with no password.
[JM-810] - Presence subscription packets sent to the server were broadcasted to all connected users.
[JM-701] - Fixed bug with roster modification when deleting shared group. (7 votes)
[JM-801] - Removing users from shared group could generate roster items in the database.
[JM-811] - Fixed case-sensitive error while authenticating users.
[JM-784] - Success data included after a SASL successful operation was not being encoded.
[JM-794] - SASL mechanisms were being offered to remote servers even before securing the socket.
[JM-796] - Fixed "null cert chain" error when trying to secure s2s connection.
[JM-789] - CN field in certificates was not being correctly parsed.
[JM-785] - Retrieving a privacy list was including two list elements in the answer.
[JM-780] - Plugin check is now based on original JAR date, not on unzip date.
[JM-786] - JDBCAuthProvider and JDBCUserProvider were using wrong property names.
[JM-812] - It was not possible to retrieve offline messages with invalid XML characters.
[JM-793] - Counter of client sessions was wrong.
[JM-783] - Admin console now displays actual bound IP address. (1 vote)
[JM-790] - Removed database scripts from the wildfire JAR.
[JM-815] - Changed element to element in response to subscription request.
[JM-861] - Moved abrupt connection closure messages to debug.
[JM-863] - XMLProperties was not able to store CDATA.
Wildfire 3.1.0 keywords