Re: [Quickfix-users] some question on QuickFix usage
Brought to you by:
orenmnero
|
From: Oren M. <or...@qu...> - 2004-12-28 21:31:19
|
The message itself will not go to your application, but the reject that =
goes out to the counterparty should via the toAdmin callback.
You should never have to send your own ResendRequest messages. QuickFIX =
is very smart about doing this on its own when necessary. The .outgoing =
file should contain everything that is sent to the counterparty, =
including ResendRequests.
I'm not sure why you can't solve your problem with a new xml. From your =
description it seems you just need an xml that declares that field as a =
string. Is there anything else?
--oren
----- Original Message -----=20
From: Alexey Zubko=20
To: qui...@li...=20
Sent: Thursday, December 23, 2004 2:02 PM
Subject: RE: [Quickfix-users] some question on QuickFix usage
Hi Oren,
=20
Thank you for the fast reply.
=20
I read this documentation of course, but it's more like a quick start =
reference.
It's easy to build a server or a client application, but if you need =
to reset the sequence number manually, for example, you have to look =
through the code.
=20
I'm absolutely agreed that validated messages are less dangerous.
But it's more danger to lose a message than to know that it was not =
passed validation.
=20
I write a client for non-QuickFix server which misuses a FIX tag =
(sends string instead of char (enum)).
I can't solve the problem by defining a new xml, I need to change the =
QuickFix source code and as a result I have a separate library for this =
particular project.
By the way, this field is not required by protocol and I really don't =
care of the value.
=20
What did you mean saying to monitor the reject message?
The message is rejected in the dictionary and is not go to my =
application class.
=20
Regarding resend:=20
Do you mean I don't need to create my ResendRequest callback to resend =
messages?
If QuickFix sends these messages by themselves should the *.outgoing =
file contains them too?
=20
=20
Thank you again.
=20
=20
Regards,
Alexey.
=20
|