That makes sense Robert. We're planning the Windows persistence work in two phases, initially SQL Server for everything and then add in the CLFS piece for the message log for systems that support it. Hopefully the SQL layer piece should be portable enough to make a SQLLite mapping fairly straight-forward.
Dave. -----Original Message----- From: Robert Greig [mailto:robert.j.gr...@gmail.com] Sent: Friday, June 12, 2009 2:25 PM To: dev@qpid.apache.org Subject: Re: Persistence FAQ for Java 2009/6/12 Andrew Stitcher <astitc...@redhat.com>: > Looking at the docs CLFS seems to be supported only since Windows 2003 > which I think would exclude the many XP systems out there, so that might > not be so good. Yes, this would be something of an issue for developer desktops. Obviously no-one is going to use XP for a production deployment, but many corporate developers have to use XP on the desktop and although virtual w2k3 or later environments may be available that is often not terribly convenient. I think a SQLLite instance (which would just need to be functional rather than performant) would be a good idea, with CLFS available for development on Vista or Windows 7 and all production use. It will be very interesting to compare the performance of the Windows broker with CLFS and Red Hat with its AIO implementation! RG --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
