[Quickfix-users] QuickFIX Functional Documentation/Expected behaviors?

[abaraff <ab...@ra...>]

I'm trying to use the .Net version and have managed to setup initiators and
acceptors, connect to remote Engines as well as my own, send messages,
receive messages and crack messages so some of the basics are working.  I've
gone through the scant documentation, have browsed the class structure and
have done about a thousand google searches, but I'm having trouble
understanding how QuickFIX is supposed work/deal with various situations. 
Is there some functional documentation that exists?  A book?

A few of the things I can't figure out:

Is there a built-class for accessing messages that have been written by the
FileLogFactory?  Am I expected to re-parse this on my own?  I don't mind
doing that, but it seems like the system is probably already doing this
somewhere.  I've looked at all the Session class methods and LogFactory
methods and don't see anything exposed that looks like it's relevant.

In the events log I can see that there are resends being done when the
system starts but I don't see any callbacks to my QuickFix.Application
object in response to them.  I don't have any problems getting callbacks
after this resyncing has taken place however.  Is this expected behavior? 
How does QuickFIX Decide which messages it will call me back on and which
ones it will hide.  Is there a way to have the application call me back with
every message for the session that was received by the previous instance of
the application on restart?

If I manually send a ResendRequest, should I get called back when the
messages arrive or are they bypassed for some reason?

Thanks,

Anthony




-- 
View this message in context: http://old.nabble.com/QuickFIX-Functional-Documentation-Expected-behaviors--tp31603621p31603621.html
Sent from the QuickFIX - User mailing list archive at Nabble.com.