On Wed, Oct 7, 2009 at 4:39 PM, Steve Huston <[email protected]> wrote:
> The way this has shaped up (and I'll be posting code soon) is that > there are two layers of plug-in: the portable store and the > storage-specific backend. The portable store offers an option to > select the backend, validates requests from the broker, and directs > the recovery; the backend knows the storage layout and manages it. Any > kind of storage can plug into the backend, SQL or otherwise. Did you end up seperating the message store stuff from the configuration data? It's something we've been looking into doing for the Java broker for a while. If this is going to land for 0.6 I'd really appreciate getting a look at it sooner rather than later so we can try to figure out a compatible schema... - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org "A witty saying proves nothing" - Voltaire --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
