[Quickfix-developers] Saving incoming messages: decision point

[John M. <jg...@jg...>]

All,

As I mentioned before, we are changing QuickFIX to support optional 
saving of incoming messages to the message store (via config 
parameter).

I see two options when it comes to the MySQLStore implementation:

1) reverse the sender and target IDs and create/update a record with 
that key
2) add another field to the key (messages table) which indicates 
incoming or outgoing

(1) may cause a problem if both sides of a session are using the same 
database-- for example, in testing

(2) involves a schema change which might cause some current users 
problems when upgrading to a future QuickFIX release that has this 
feature

Does anyone have a preference?  I'm inclined to go with (1)...

Thanks,
John

PS-- the motivation for this is to help in applications that actually 
use the message store for other processing, such as in generation of 
OATS reports and for other audit procedures.  I'm not sure that I want 
to use the MySQL log facility for this since it involves writing 
outbound messages to the database twice (= performance hit)... and 
could result in more than one entry per sequence number (= dups).