Openfire (Wildfire/Jive Messenger) and (Spark; Pandion) - [3] :: В помощь системному администратору

Теперь Jive messenger называется Wildfire Server.

Цитата:

Starting with the 2.4.0 release, Jive Messenger is now Wildfire Server. Changing the name of a well-established project is never something to be taken lightly. However, several factors convinced us that this was the right choice:

Simply a Better Name

The are lots of "Messengers" out there -- and our project is too important to be a wallflower. When we released the Spark IM client, the reaction to the name was almost universally positive. We wanted a name for the server that would be thematically linked and of equal weight; we feel that Wildfire meets those goals and it's a name we're proud to use as more and more people discover the powerful combination of Wildfire and Spark.

A Client, a Server?

Another good reason to not be connected to the many "Messengers" is to more clearly communicate that ours is a server product and not an IM client. Wildfire Server should put that to rest.

Dedication to Performance

Wildfire simply sounds faster than Jive Messenger, but more importantly we're committed to making Wildfire the fastest, most scalable, and fault-tolerant server available. As a first step, we've been hard at work on server optimizations, which have made Wildfire at least 33% faster than Jive Messenger. We're also working on the Pampero Project to provide the next big leap in scalability.

И вышла новая версия:

2.4.0 -- December 15, 2005

New Features
[JM-480] - Server performance was optimized.
[JM-333] - Added support for JEP-0138 (stream compression). (1 vote)
[JM-486] - Added support for closing idle c2s connections. (4 votes)
[JM-479] - Upgraded to JDK 1.5.0_06
Bug Fixes
[JM-490] - When a group was not found in LDAP an exception was not being thrown.
[JM-491] - Packets for remote servers were sometimes lost.
[JM-483] - Kicking old client due to resource conflict was not letting the new client log into the server.
[JM-481] - Last packet sent before closing the client connection was not being processed.
[JM-482] - An empty roster is now returned when anonymous user requests their rosters.
[JM-484] - IQ packets of type <auth> and <register> were not being offered when TLS was disabled.
[JM-488] - Fixed problem where threads may wait forever trying to obtain a db connection from the pool.
[JM-487] - JDBC drivers were upgraded.
[JM-485] - Source build was failing.

Модерирует : lynx, Crash_Master, dg, emx, ShriEkeR
emx (19-07-2007 13:15): http://forum.ru-board.com/topic.cgi?forum=8&topic=22500#1	Версия для печати • Подписаться • Добавить в закладки
Страницы: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101