Re: [Quickfix-developers] Tibco Rendezvous Implementation Question
Brought to you by:
orenmnero
From: Oren M. <om...@ri...> - 2004-03-01 20:05:51
|
John, Can you clarify the architecture? I think this is what you are doing. =20= You have clients connecting in through QuickFIX (via socket?), who send=20= order, you take those orders and publish them on the TIB which is=20 picked up by you're matching engine (in FIX?), you then match the=20 orders and publish them back, which is picked up by a process that then=20= needs to send the matched order back to the originating clients through=20= QuickFIX. Is this correct? Now I guess the question is how you are changing the routing=20 information when you publish to the matching engine. Essentially to=20 send things back to the same client you will have to have the correct=20 beginstring, sendercompid, and targetcompid. Is this information that=20= you have lost in the transformation to the order matcher or is it still=20= around, or can it be derived from the message in some other manner? --oren On Mar 1, 2004, at 10:26 AM, Dahl, Jon wrote: > We are going to be talking to our Matching Engine over Tibco with a > pub/sub communication mechanism. > There will be only one connection to the Tibco bus and all > requests/responses will come over that one > connection. > > Is there anyway to inject the response messages into QuickFIX... by=20 > that > I mean making sure they go to > the correct client. Responses from the engine will be in FIX format. > > > > Thanks, > > JD > > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers |