[mashup-dev] IM support for the mashup server

[Paul Fremantle]

I thought Sanjiva and I had impressed on the whole development team that 
we were no longer building components such as IM support on a "per 
product basis" but moving to a model where we try to make this support 
common across all our platforms!

There is certainly a requirement in ESB for IM support - most of our 
competitors have it.

Paul

Keith Chapman wrote:
> Is there a necessity of having this IM code in commons?
> 
> My feeling is that it can be in the mashup code base.
> 
> Thanks,
> Keith.
> 
>   Sanjiva Weerawarana wrote:
>> Very cool! U have to do a mashup which IMs when there's an earthquake :).
>>
>> There's no need to separate the server name in Jabber- that's a JID 
>> (Jabber ID) .. it should be user at server/resource and the whole thing 
>> can be in the "username" parameter - just rename it to user id.
>>
>> Please keep the GPL code *carefully* separated and make sure we don't 
>> distribute it as part of our codebase! We need to ship that separately 
>> to adhere to the license.
>>
>> Sanjiva.
>>
>> Keith Chapman wrote:
>>> Hi all,
>>>
>>> I've been looking into IM support for the mashup server. I was able 
>>> to get msn, yahoo, Jabber, aim and icq working. There is no single 
>>> library that handles the various protocols, but there are independent 
>>> jars that perform the individual tasks. The following are the 
>>> labraries that will be needed and there sizes.
>>>
>>> Protocol
>>>     Library
>>>     License
>>>     Size
>>> yahoo
>>>     ymsg_network_v0_6.jar
>>>     GPL
>>>     104K
>>> MSN
>>>     jml-1.0b2.jar + cindy.jar
>>>     Apache License
>>>     285K
>>> Jabber
>>>     smack.jar + smackx.jar
>>>     Apache License     677K
>>> AIM
>>>     joscar-client.jar+ joscar-common.jar+ joscar-protocol.jar
>>>     LGPL
>>>     1209K
>>> ICQ
>>>     joscar-client.jar+ joscar-common.jar+ joscar-protocol.jar      
>>>
>>> Both AIM and ICQ woks with the same Library, but I have used the 
>>> latest version build using current svn. There is not much active 
>>> development happening though (The last change date is 2007-01-05).
>>>
>>> The only issue is that the yahoo library is under GPL. There are no 
>>> alternate open source java libraries for yahoo. All protocols are 
>>> pretty much the same and follow the following sequence.
>>>
>>> 1. Create a connection.
>>> 2. Login using the username and password.
>>> 3. Send the message.
>>>
>>> The only protocol that differs is jabber where you have to give the 
>>> jabber server.
>>>
>>> It will be nice to abstract out a java API that we can later wrap as 
>>> a JavaScript API. The obvious methods that we need will be. How are 
>>> we going to fit in the servername for jabber? (The same will be 
>>> needed if we are to support IRC. Do we need support for IRC too?).
>>>
>>> public boolean login(String username, String password);
>>> public void connect();
>>> public void disconnect();
>>> public void sendMessage(String message);
>>>
>>> Thanks,
>>> Keith.
>>>
>>>
>>> _______________________________________________
>>> Mashup-dev mailing list
>>> Mashup-dev at wso2.org
>>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>>
>>
> 
> 
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
> 

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com