10 October 2007
A new version of the BuddyStream SDK has been released.
More information on the current company highlight
   
buddystream buddystream products download instant messaging sdk

Downloads - BuddyStream platform:

Please complete the following optional form before downloading BuddyStream. It is important to contact us if you will be requesting a license. We cannot send you license keys otherwise.





  1. Make sure that a Java 5 compliant Java virtual machine is available. These are obtainable at no cost from Sun Microsystems and other vendors. The following steps assume that this virtual machine is the default for the system.
  2. Download the platform's installer and start it by clicking on its icon or by entering java -jar BuddyStream-3.4.1.jar at the command–line.
  3. Follow the instructions given on the screen. If you intend to run the bundled software, you should let the installer generate a software license request. You do not need a software license if you only want to browse the documentation or use the development libraries.
  4. Once we receive the request we will send you a license according to your needs. Place the file we send you (usually named server.lic) inside directory licenses. We process requests manually, so it might take us up to two business days to get back to you.
  5. While you wait for the license, you may want to install the latest hotfix. You should download the archive file from the link above and expand its contents directly inside the directory where BuddyStream was installed.

What has changed recently in the BuddyStream platform:

Version 3.4.1 released on 2007-10-10
  • The Windows Live Messanger (formerly MSN Messenger) plug-in was updated to the latest version of the protocol, making it possible to interoperate with Yahoo Messenger contacts, send and receive offline messages, set custom status messages and more.
  • The Yahoo Messanger plug-in was updated to the latest version of the protocol, making it possible to interoperate with Windows Live Messenger contacts (formerly MSN Messenger).
  • All new Gadu-Gadu and Xfire plug-ins were added to the platform.
  • A content channel for browsing ICal feed was added as well.
  • Lots of bugs were fixed across many of the plug-ins.
  • Some performance improvements were made to the most popular plug-ins.
  • We reduced the memory usage in our reference client-side implementation in Java. Now it can escalate to thousands of simultaneous connections when using our non-blocking I/O connector. And the best thing is that it is transparent to the programmer!
Hotfix #1 released on 2007-11-14
  • Fixed a packaging issue that caused a dependency on Java 6.
Hotfix #2 released on 2007-11-16
  • Fixed an MSN log-in issue where the OS version was rejected for being too long for some Linux kernels.
  • Fixed an MSN log-in issue where the user password was rejected for being too long.
Hotfix #3 released on 2008-01-18
  • Reworked multi-chat behavior so that it's only used for locally initiated MUCs or when a remotely initiated chat contains more than two users [1.4.4].
  • Fixed initial presence status listing on Yahoo! Messenger.
  • Minor fix for OSCAR that caused an exception to be logged.
Hotfix #4 released on 2008-02-08
  • Avoid random Yahoo! disconnections.
Hotfix #5 released on 2008-07-19
  • Updated ApplicationID on MSN library. Microsoft started blocking the old one, as it belonged to an old version of their client.
Hotfix #6 released on 2008-08-11
  • Updated CA certificates to allow secure connections to the new MSN services.
  • Implemented new MSN authentication methods required to interoperate with the MSN network as of recently.

Upgrading from a previous version.

From 3.2.0
  • A change in the database schema was introduced. The direction of the association between tables Roster and Identity was changed: Column ident_id was removed from the former and rid (roster Id) was added to the latter. You need to update your schema, or drop the tables and recreate from the scripts supplied in the doc directory.

    The following scripts, adapted to the SQL dialect of your database engine, should be used to update the database schema without losing any of the data contained.

    MySQL
    ALTER TABLE Identity ADD COLUMN rid INT;
UPDATE Identity, Roster SET Identity.rid = Roster.id WHERE Roster.ident_id = Identity.id;
ALTER TABLE Roster DROP COLUMN ident_id;
    SQL Server
    ALTER TABLE [Identity] ADD rid INT;
UPDATE [Identity] SET [Identity].rid = Roster.id FROM [Identity], Roster WHERE Roster.ident_id = [Identity].id;
ALTER TABLE Roster DROP COLUMN ident_id;
  • An external process should be launched periodically to clean up old rosters from the database. See the BuddyStream manual for more information and sample scripts.

Find more information on previous versions of the platform at our software respository.