Steve, Martin,
It would be great to get fully competent ASL licensed components
throughout -- our out of box experience is lacking becuase of the
"some assembly required" aspects of getting a production ready
persistent broker set up.
For a DB implementation for C++ that is ASL compatible, I think
SQLite (public domain) is probably the only option.
It's performance won't be stellar, but it could be very good and its
documented robustness characteristics seem good too.
Properly abstracted, it would also allow the core of a pluggable SQL
store with SQLite as the default.....
Cheers
John
At 15:39 11/06/2009, you wrote:
Hi Martin,
> Really we should just be sorting out an ASL store. The Java Broker's
> Derby store is good but IIRC still has a couple of bugs that could
do
> with addressing.
>
> I've got some time to do some refactoring based on the designs on
> Message Storage that are on the wiki so hopefully things will
improve
> in this area soon.
Ok - I'm interested in your efforts here.
> Are there any plans from the C++ side to make an ASL compatible
> persistent store?
I have funding from Microsoft to do a persistence store for C++ on
Windows. I'm not 100% certain of the licensing, but I'll check.
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
