|
JBuddy Server Release Notes
Release 3.2 Build 111216 - December 16, 2011
Release 3.1 Build 100815- August 15, 2010
Build 100305 - March 5, 2010
Build 090401 - April 1, 2009
Release 3.0 July 18, 2006
DB Notes: Release 2.0 Build 0913
Technical Notes: Several new features and fixes require the new JBuddy 5 SDK for the complete fix. Security/Encryption - TLS/SSL: With the new JBuddy 5 release, the JSC client can be configured to connect to the JBuddy Message Server in three ways: only secure, attempt secure first, then drop back to unencrypted (default specified in JSC.properties), and unencrypted (the only option in pre-2.0 servers). In order to enable TLS/SSL, the Server must be running on Java 5 runtime environment and the jbuddy.use_ssl=true System property must be set in the wrapper-jbuddy.conf prior to the start of the Server. Clients using pre-JBuddy 5 SDKs must upgrade to JBuddy 5 SDK to connect to TLS/SSL enabled Server. NickName: With the new JBuddy 5 SDK, JSC Clients can now call setNickName(nickName) and have it persist to the Server DB. In order to accomodate this change the Server DB schema was modified. See DB Notes below. Concurrent User License: In 'Demo Mode', the Server supports a default of fifty (50) concurrent connections. To go beyond the default, the Server requires a new license.lic file to be copied to the lib directory of the Server before starting the Server. This license file tells the Server what features and how many you have permission to use. This file is not editable and if it is, will result in an invalid license error and the Server will shut down. Buddy Idle Time: The Server was corrected to store the DateTime when the client reported IDLE status instead of just the number of minutes idle (relative to what?). In order to accomodate this change the Server DB schema was modified. See DB Notes below.
DB Notes:
Build 0215
Technical Notes: Message Archival: A new DB table Messages was added to store messages as they pass throug the server. To disable message archival logging, the jbuddy.disable_message_archive=true System property must be set within wrapper-jbuddy.conf.
DB Notes:
Build 0210
Technical Notes: Corruption: DateFormatter was found to be thread-unsafe and exhibited corruption problems when used by multiple threads under a heavily loaded server. Use of DateFormatter was replaced with a synchronized subclass. Build 0127
Build 0125
Technical Notes: NAT Traversal: File Transfer for the JSC protocol uses port 1424. Either the sender or the recipient must have that port open on any firewalls between them for the file transfer to work. That said, the Server will report the external IP address of a client behind a NAT to the other client in order to attempt to setup the file transfer. Build 0121
Build 0722
|