Re: [Quickfix-developers] non logged-on messages

[John G. <joh...@wa...>]

Hi (again),

> Seriously though. You raise some interesting points about keeping closer 
> track of which messages could/could not have possibly been sent previously. 
> This is something that the SessionState could perhaps keep track of, but it 
> would complicate the code for questionable benefit.
> What is the harm in sending a message that might never before have been sent 
> as a PossDup? 

I know at least one system that just drops them, but they are wrong and 
should use fonctionnal data to ensure uniqueness as you describe.

The only thing that bugs me is that I don't like the idea of relying on 
the counterparty to basically say "eh, are you sure you did not forget 
something ?" when I perfectly know I did. As I understand it, resend 
resquests are a way of recovering unforeseen errors, not a means to 
say "it's time to empty the sending queue".

It works like this, it's just a question of having the right information. 

Now on the other hand : why then in examples, disable totally the 
resending of a message tagged (we know wrongly, because it works like 
this) PossDup ? In fact, why even try to disable it ? It is sure to cause 
losses of application messages that will go totally unnoticed for a long 
time. 

Sincerely,
JG