Re: [Quickfix-developers] Tibco Rendezvous Implementation Question

[Oren M. <om...@ri...>]

Yes you can.  FIX::Session::sendToTarget was made a static method to=20
solve this very problem, that you can't always predict when or where=20
you will want to send a message.  Anytime you want to send a message=20
from anywhere in the process, you can use this call to do it.  It makes=20=

no difference if you are in the application interface or in an obscure=20=

thread called by some wacky third party library called tibco.  As long=20=

as you have a sessionid or the correct routing fields are set in the=20
message header, the message will find its way to the correct client.

--oren

On Mar 1, 2004, at 2:14 PM, Dahl, Jon wrote:

> Oren,
> =A0
> You are correct in your assumptions. I will be returned the correct=20
> SenderCompId, TargetCompId, and BeginString.
> =A0
> The Tibco interface will be implemented within the same process - not=20=

> outside.
> =A0
> My main concern is getting the message from the Tibco Callback=20
> function to the right client. Correct me if I am wrong here, but I=20
> couldn't call FIX::Session::sendToTarget()=A0from outside the=20
> Application interface could I?
> =A0
> =A0
> =A0
> -----Original Message-----
> From: Oren Miller [mailto:om...@ri...]
>  Sent: Monday, March 01, 2004 1:53 PM
> To: Dahl, Jon
> Cc: qui...@li...
> Subject: Re: [Quickfix-developers] Tibco Rendezvous Implementation=20
> Question
>
> 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=20
> send 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=20
> then needs to send the matched order back to the originating clients=20=

> through 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=20
> still around, or can it be derived from the message in some other=20
> 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