On 27 May 2010 00:55, Rajith Attapattu <[email protected]> wrote:
> If we upgrade to mina 1.1.7 then we could easily get rid of
> backport-util-concurrent.jar.
> With the changes I proposed in QPID-2629 we reduce this a bit further as well.
>
> For the client release, if we don't ship the tests then with the above
> changes we could get somewhere close to ~ 2.3 MB.
> Here's the break down.
>
> 532K    build/lib/qpid-client-0.7.jar
> 32K     build/lib/mina-filter-ssl-1.0.1.jar
> 4.0K    build/lib/plugins
> 1.4M    build/lib/qpid-common-0.7.jar
> 24K     build/lib/qpid-all.jar
> 308K    build/lib/mina-core-1.0.1.jar
> 28K     build/lib/geronimo-jms_1.1_spec-1.0.jar
> 16K     build/lib/slf4j-api-1.4.0.ja

Don't for get to count your favourite slf4j binding to make the total
size of a usable client.

> Rajith
>
> On Wed, Mar 31, 2010 at 2:51 PM, Joshua Kramer <[email protected]> wrote:
>>
>>> would expect a message queue client to be not bigger than ~500KB
>>> (dependencies included and fully compressed with pack200+lzma)
>>
>> 500KB would be nice.  Some of my "science experiments" target Java-based
>> platforms with 1MB of Flash and 1MB of RAM.  For now I open sockets to a
>> server, and the server in turn does any queue manaement things as needed.
>>
>> http://www.maxim-ic.com/products/microcontrollers/tini/
>>
>> Cheers,
>> -JK
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:[email protected]
>>
>>
>
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>



-- 
Martin Ritchie

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to