On Thu, May 27, 2010 at 12:06 PM, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 27/05/2010 01:55, Rajith Attapattu a écrit : > >> 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 > > Do you think it could be possible to split the qpid-common jar? A large part > of this jar consists of the framing for the different versions of the > protocol. By removing the 0-8, 0-9 and 0-91 classes the jar is reduced by > 56%. > > I imagine there could be one jar per version, and the user would keep only > those he needs.
I was also thinking along the same lines. One of the key requirements for the Java client is to able to support multiple protocol versions. Splitting into multiple jars based on protocol versions should be ok as long as we preserve that. The default client should include all jars, but in documentation we could mention that they can just copy only the jars they are interested in. I think the same can be done for the transports as well. Since 0-10 client doesn't use mina, anybody who is only interested in 0-10 can easily get rid of the mina jars. Another more important thing to do is to have look at all the classes in common and get rid of classes that are not used. Also if classes are only used on the broker side, then they should be moved to the broker module. > Emmanuel Bourg > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
