Messages sent to multiple destinations

, ,
1

Imported from previous forum

2

[ original email was from Lisa Linton - ]
Does the FIX protocol include functionalities which allow a message to be sent to multiple destinations? That is, one message generating multiple copies to be sent to different recipients? If such functionality exists, how is it handled?

3

[ original email was from Jean-Pierre Schiltz - ]
> Does the FIX protocol include functionalities which allow a message to be sent to multiple destinations? That is, one message generating multiple copies to be sent to different recipients? If such functionality exists, how is it handled?
>
See "exclusion of a target company from IOI distribution" before - I agree with you something should be done !

4

[ original email was from Bob Lamoureux - ]
> > Does the FIX protocol include functionalities which allow a message to be sent to multiple destinations? That is, one message generating multiple copies to be sent to different recipients? If such functionality exists, how is it handled?
> >
> See "exclusion of a target company from IOI distribution" before - I agree with you something should be done !
>

This functionality is an application level issue !!! Each fix message must ultimately be sent to a destination directly. So how would specifying a multiple list in the message itself help ???

What you need/want is an application level process that iterates thru the list and builds the appropriate messages. FIX is not a broadcast system so this multi-destination syntax is not appropriate.

5

I agree wholeheartedly that this is an application level issue and feel that there are several ways to accomplish what you’re describing at an application level.

> > > Does the FIX protocol include functionalities which allow a message to be sent to multiple destinations? That is, one message generating multiple copies to be sent to different recipients? If such functionality exists, how is it handled?
> > >
> > See "exclusion of a target company from IOI distribution" before - I agree with you something should be done !
> >
>
> This functionality is an application level issue !!! Each fix message must ultimately be sent to a destination directly. So how would specifying a multiple list in the message itself help ???
>
> What you need/want is an application level process that iterates thru the list and builds the appropriate messages. FIX is not a broadcast system so this multi-destination syntax is not appropriate.
>