I'm using QuickFix 1.13.3 with the .Net 4.0 wrapper.
Working with QuickFix 1.13.3 in a .Net environment, it's easy to forget that
the Message objects being passed to FromApp() or FromAdmin() might be freed
at some point in time, even if I'm still holding a reference to it.
That's what I'm trying to figure out - whether I can hold and use a
reference to a Message object that I received in FromApp or FromAdmin after
that method completes. One reason to hold on to a Message object beyond the
FromApp or FromAdmin is to queue that Message object and have it processed
by another thread.
I see in Application.h that the Message object is created using the
MessageFactory.create function which seems to create a managed
QuickFix::Message object. Then, setUnmanaged(FIX::Message& unmanaged)is
called so it appears to me as if the message passed to FromApp or FromAdmin
has an unmanaged component.
So I hope some out there can give me a definitive answer regarding the
lifetime of the Message object and *if* the lifetime does not extend beyond
FromApp or FromAdmin, what's a good way to get around this limitation
(besides switching to QuickFix/Net).
--
View this message in context: http://old.nabble.com/Processing-a-QuickFix%3A%3AMessage-on-a-background-thread-after-completion-of-Application.FromApp-tp34690218p34690218.html
Sent from the QuickFIX - User mailing list archive at Nabble.com.
|
