Imported from previous forum
We have a FIX gateway implementation that its only function is to route drop copies to FIX clients.
A client is wondering if our server can handle “PossResend” (field #97) set to “Y”.
this field is defined as optional header field in our specification for our FIX gateway (which includes drop copies as well as other message types).
I realize this is an application message field and must be handled at the application layer.
We don’t have any special provision to deal with it. But I am wondering how this field being set applies to our scenario where we are simply routing messages one way to the FIX client. They don’t send us anything except session level messages such as replay request, logon, etc. that our FIX server vendor product deals with.
can someone think of any usage for PossResend=Y where we are routing messages one way like above situation ? i.e. a situation where application layer would care about this field in the above scenario ?
thanks
J.
[ original email was from Stratos Efstratiou - stratos.efstratiou@nasdaq.com ]
The PossResend is used to resend a message that may have been sent before and gives the receiver notice to check this message as a possible duplicate.
If your FIX Gateway drop copies to a separate FIX connection, then this tag is not necessary.
Why is your client looking for PossResend?
We have a FIX gateway implementation that its only function is to route
drop copies to FIX clients.A client is wondering if our server can handle “PossResend” (field #97)
set to “Y”.this field is defined as optional header field in our specification
for our FIX gateway (which includes drop copies as well as other
message types).I realize this is an application message field and must be handled at
the application layer.We don’t have any special provision to deal with it. But I am wondering
how this field being set applies to our scenario where we are simply
routing messages one way to the FIX client. They don’t send us anything
except session level messages such as replay request, logon, etc. that
our FIX server vendor product deals with.can someone think of any usage for PossResend=Y where we are routing
messages one way like above situation ? i.e. a situation where
application layer would care about this field in the above scenario ?thanks
J.
They are not looking for PossResend being set from us. They want to know what happens if they sent it to us and if we can “handle” it. We simply ignore it.
that answers my question pretty much. It might be their implementation simply sets that flag but it adds no value at our end and it is mainly for their convinience.
thanks much.
The PossResend is used to resend a message that may have been sent
before and gives the receiver notice to check this message as a possible
duplicate.If your FIX Gateway drop copies to a separate FIX connection, then this
tag is not necessary.Why is your client looking for PossResend?
We have a FIX gateway implementation that its only function is to
route drop copies to FIX clients.A client is wondering if our server can handle “PossResend” (field
#97) set to “Y”.this field is defined as optional header field in our specification
for our FIX gateway (which includes drop copies as well as other
message types).I realize this is an application message field and must be handled at
the application layer.We don’t have any special provision to deal with it. But I am
wondering how this field being set applies to our scenario where we
are simply routing messages one way to the FIX client. They don’t send
us anything except session level messages such as replay request,
logon, etc. that our FIX server vendor product deals with.can someone think of any usage for PossResend=Y where we are routing
messages one way like above situation ? i.e. a situation where
application layer would care about this field in the above scenario ?thanks
J.