RE: [Quickfix-developers] onMessage callback

[<or...@qu...>]

Messages get delegated to the MessageCracker by calling the crack
method.  You generally make this call from the fromApp method.  fromApp
gives you a generic message type.  While you can do everything you need
with this class, the cracker will cast the message to a more specific
type.  This gives your messages type safety and provides and
alternative to using switch statements to segment your logic.

--oren

> -------- Original Message --------
> Subject: RE: [Quickfix-developers] onMessage callback
> From: Shankar Krishnan <skr...@jw...>
> Date: Tue, November 08, 2005 2:44 pm
> To: qui...@li...
> Cc: Shankar Krishnan <skr...@jw...>
> 
>         
>  Thanks,   I looked at the "executor" example program. If I understand correctly, then fromApp is the entry point into FIX client application, how do messages get delegated to Messagecracker and hence onMessage, Is this part of the quickfix design ?       
>  
>    From: Caleb Epstein [mailto:cal...@gm...] 
>  Sent: Tuesday, November 08, 2005 2:48 PM
>  To: Shankar Krishnan
>  Cc: qui...@li...
>  Subject: Re: [Quickfix-developers] onMessage callback      
>  On 11/8/05, Shankar Krishnan <skr...@jw...> wrote: 
>  
> 
> I only see references to onCreate,onLogon,onLogout,toAdmin etc in the documentation. 
> 
> However I see donot see any reference to onMessage. If we have fromApp which is what 
> 
> I should care about, what does onMessage do. I did look up the documentation, but see 
> 
> Any flow diagrams what will tell me how the message flows to and from the FIX engine.  
>  The onMessage callbacks live in the version-specific FIXxx::MessageCracker classes.  Take a look at the "executor" example program for sample usage.    
>  -- 
>  Caleb Epstein
>  caleb dot epstein at gmail dot com