[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] Java client code

To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] Java client code
From: Michele Laghi <laghi at swissinfo.org>
Date: Tue, 07 Sep 2004 23:54:17 +0200
In-reply-to: <20040907205802.30307.qmail at web52404.mail.yahoo.com>
Organization: Eclettic Technologies
References: <20040907205802.30307.qmail at web52404.mail.yahoo.com>
Reply-to: xmlblaster at server.xmlBlaster.org
Sender: owner-xmlblaster at server.xmlBlaster.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

Hi Steve, this issue has been on the table and we have to tackle it soon or later. Since this has not been on top of our priority list (functionality first) we did'nt have the (spare) time to do anything about that yet. I can't either say for sure when this will be done.

Meanwhile, if the reason is the big jar size and you are in urge, you could strip it down with some tool like proguard (http://proguard.sourceforge.net/).


Greetings
Michele

Steve Mentzer wrote:

I am trying to isolate the xmlBlaster Java client code from the server
code but I'm having a lot of trouble doing so.  Is this possible?  I'd
like to create a jar that has just the classes a client would use and no
server classes (just like the C++ client).  It seems like the Java client
and server code is tightly coupled.  If so, will this be changing anytime
soon?  Thanks,

Steve Mentzer

--
Michele Laghi
mailto:laghi at swissinfo.org
tel. +46 8 7492952 / mob. +46 70 4103964
http://eclettic.tripod.com
http://www.xmlBlaster.org

References:
- [xmlblaster] Java client code
  - From: Steve Mentzer <sgmentzer at yahoo.com>

Prev by Date: [xmlblaster] Java client code
Next by Date: [xmlblaster] What happens to pubed msgs when history que is full?
Previous by thread: [xmlblaster] Java client code
Next by thread: [xmlblaster] What happens to pubed msgs when history que is full?
Index(es):
- Date
- Thread