Re: [Quickfix-users] Clarification on Quickfix/J and Quickfix
Brought to you by:
orenmnero
From: Steve B. <sb...@sm...> - 2006-08-09 21:26:50
|
> Back when Quickfix/J came out with version 1.0 (I > think) the statement was made that it was going to be > developed independently or something to that effect. Hi Mike, QuickFIX/J has always been developed, more or less, independently although Oren and I regularly discuss topics that affect both products. The announcement was about creating a separate project management and information web site for QuickFIX/J, including a separate Subversion repository. Other than that, the=20 collaboration between the projects hasn't changed=20 significantly. =20 > What is the relationship between the two projects? Are > the developers working on both projects? The development is done by separate groups of developers with Oren leading the C++ and C++-based wrapper development (Java JNI, scripting languages) and with me leading the 100%=20 Java development. > QuickFix/J claims compatibility with QuickFix, at what > level is it compatible? (Features, config files). For > instance, would QuickFix/J be able to load a config > file for QuickFix 1.12.1? The goal is that the QuickFIX JNI-based library can be replaced with a QuickFIX/J JAR file and the Java applications will continue to work. This means the Java API and configuration files are backward compatible. In other words, QFJ is backward=20 compatible with the JNI API but not vice versa. There=20 are a few places where the two libraries are not 100% backward=20 compatible. For example, QuickFIX/J relies on JDBC drivers rather=20 than having database-specific log and message store classes. However,=20 this would be a minor change for most applications. QFJ uses a slightly=20 different format for the file-based message store. Any QF JNI data=20 files should be removed before using QFJ. This is usually not a problem since it's done between FIX sessions. As for configuration, there may be one or two options in 1.12.1 that are not in QFJ 1.0.1. The releases are not synchronized so there may be a lead or lag of features between the implementations. For example, I may release a QFJ version with configuration features that are still unreleased in the C++ version. Generally though, QFJ will slightly lag the C++ implementation. Regards, Steve |