Re: [Quickfixj-users] Implementing Custom Logons

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

It's pretty much just a play on quick fix. As in, "I need FIX  
connectivity now, I wish there was some sort of quick fix."  When  
were choosing the name, and QuickFIX was the most likely candidate,  
some guy in one of the financial rags in regards to implementing the  
fix protocol said something along the lines of "there is no quick  
fix".  That sold it for us.  From then on if you needed FIX  
connectivity, there would be a quick fix.  In part it is the  
simplicity of getting up and running from a code standpoint, but also  
from a licensing, accounting, distribution etc.  You just don't have  
to go through any departments to get up and running.  A single  
developer can start prototyping right away without dealing with any  
of these or asking anyones permission.

--oren

>> P.S.  Does the "Quick" in QuickFIX refer to how quickly messages are
>> processed, how quick it is to build an application or both?  I was  
>> looking
>> for some performance numbers but didn't see anything.
>
> Oren selected the name, so I'll defer to him since I don't know how
> he selected it. For QFJ performance numbers, take a look at the
> QuickFIX C++ list. There were some numbers posted there recently.