Thread: [Quickfix-users] Post-processing
Brought to you by:
orenmnero
From: Richard H. <rh...@pe...> - 2011-04-14 18:51:20
|
Hello. I have an application that sends information to a variety of destinations, through a variety of routes. The application works well. Now it is emerging that some of those destinations want special treatment. “Oh, when you send me my symbol name, please append this string to it. It will help me in my processing.” I suspect that a lot of destinations will want some particular thing slightly different. I can imagine my neat, simple application getting festooned with crap. It would be nice to do some post-processing. After the application has finished its work, and thinks the fix message is ready to send out, it checks whether there is a script stored for this destination. If there is, it runs the string representing the fix message through the script, and sends the result. Perhaps one can embed awk, or the perl regular expression processor. Will I break anything if I pull the string representing the fix message back from the QuickFix engine right before I call Session.sendToTarget, possibly change the string, give it back to the engine, and call sendToTarget? Regards, Rick Rick Hedin Software Engineer PE∆K6 Investments 141 W. Jackson Blvd. Suite 500 Chicago, Il 60604 D: (312) 362-4343 E: rh...@pe...<mailto:rh...@pe...> ______________________________________________ See http://www.peak6.com/email_disclaimer.php for terms and conditions related to this email |
From: Hei C. <str...@ya...> - 2011-04-15 00:35:51
|
Not sure why you want to do a regular expression on the entire raw FIX message. If you want to apply regular expression or some sort on a tag value, you can do such processing in toApp() or toAdmin(). ----- Original Message ---- From: Richard Hedin <rh...@pe...> To: "qui...@li..." <qui...@li...> Sent: Thu, April 14, 2011 11:36:08 AM Subject: [Quickfix-users] Post-processing QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX Support: http://www.quickfixengine.org/services.html Hello. I have an application that sends information to a variety of destinations, through a variety of routes. The application works well. Now it is emerging that some of those destinations want special treatment. “Oh, when you send me my symbol name, please append this string to it. It will help me in my processing.” I suspect that a lot of destinations will want some particular thing slightly different. I can imagine my neat, simple application getting festooned with crap. It would be nice to do some post-processing. After the application has finished its work, and thinks the fix message is ready to send out, it checks whether there is a script stored for this destination. If there is, it runs the string representing the fix message through the script, and sends the result. Perhaps one can embed awk, or the perl regular expression processor. Will I break anything if I pull the string representing the fix message back from the QuickFix engine right before I call Session.sendToTarget, possibly change the string, give it back to the engine, and call sendToTarget? Regards, Rick Rick Hedin Software Engineer PE∆K6 Investments 141 W. Jackson Blvd. Suite 500 Chicago, Il 60604 D: (312) 362-4343 E: rh...@pe... ________________________________ See http://www.peak6.com/email_disclaimer.php for terms and conditions related to this email |
From: Martin D. <ma...@ma...> - 2011-04-15 04:06:13
|
On Thu, Apr 14, 2011 at 06:36:08PM +0000, Richard Hedin wrote: > I have an application that sends information to a variety of > destinations [and] it is emerging that some of those destinations > want special treatment. [...] It would be nice to do some > [in-process] post-processing [perhaps with] awk, or the perl regular > expression processor. > > Will I break anything if I pull the string representing the fix > message back from the QuickFix engine right before I call > Session.sendToTarget, possibly change the string, give it back to > the engine, and call sendToTarget? Won't you risk invalidating BodyLength? Usually it's best to leave the destination-specific processing as late as reasonable. For some volume/fault-tolarance goals, separate forwading "destination" processes that do per-destination post-processing might make the most sense. > Regards, > > Rick Martin |
From: Kenny S. <ks...@co...> - 2011-04-15 13:23:53
|
One way to do this is to use this callback: toApp( Message& msg, const SessionID& sessionID) And then take some code path based on the SessionID that is passed in. -- Kenny Stone Connamara Systems, LLC On Thu, Apr 14, 2011 at 10:29 PM, Martin Dengler <ma...@ma...>wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > > On Thu, Apr 14, 2011 at 06:36:08PM +0000, Richard Hedin wrote: > > I have an application that sends information to a variety of > > destinations [and] it is emerging that some of those destinations > > want special treatment. [...] It would be nice to do some > > [in-process] post-processing [perhaps with] awk, or the perl regular > > expression processor. > > > > Will I break anything if I pull the string representing the fix > > message back from the QuickFix engine right before I call > > Session.sendToTarget, possibly change the string, give it back to > > the engine, and call sendToTarget? > > Won't you risk invalidating BodyLength? > > Usually it's best to leave the destination-specific processing as late > as reasonable. For some volume/fault-tolarance goals, separate > forwading "destination" processes that do per-destination > post-processing might make the most sense. > > > Regards, > > > > Rick > > Martin > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > > |