Re: [Quickfix-users] [Quickfix-developers] Quickfix for FIX 5.0.....

[Alvin W. <AW...@FF...>]

We went to FPL's Technology Focus Day 2006 today:
http://www.fixprotocol.org/documents/2893/FPL_Technology_Focus_Day.pdf

Besides transport independence framework and running different FIX versions
on the same session, FIX 5 will use XML to organize repository (some
similar to quickfix's xml dictionaries). Just wonder if QuickFIX and
QuickFIX/J can leverage that directly. Another big thing is FAST protocol.
Do QuickFIX and QuickFIX/J plan to support FAST?

Thanks.



                                                                          =
=20
             Oren Miller                                                  =
=20
             <oren@quickfixeng                                            =
=20
             ine.org>                                                   To=
=20
             Sent by:                  Eranga                             =
=20
             quickfix-develope         <pe...@ri...>      =
=20
             rs-bounces@lists.                                          cc=
=20
             sourceforge.net           qui...@li...urcefor=
=20
                                       ge.net,                            =
=20
                                       qui...@li...=
=20
             10/25/2006 02:56          t                                  =
=20
             AM                                                    Subject=
=20
                                       Re: [Quickfix-developers] Quickfix =
=20
                                       for FIX 5.0.....                   =
=20
                                                                          =
=20
                                                                          =
=20
                                                                          =
=20
                                                                          =
=20
                                                                          =
=20
                                                                          =
=20



QuickFIX Documentation:
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

Well the first cut will be likely to use the Session Protocol as the first
supported transport for application messages.=A0 This can be implemented wi=
th
relatively little change to the architecture as it is pretty similar to how
the previous versions work already.=A0 This will require supporting the new
versioning constructs while maintaining backwards compatibility with the
old ones.=A0 There will probably have to be some changes to how data
dictionaries work, since I guess we will need two of them.

The first release of QF with 5.0 support will probably only implement
transporting application messages over the session protocol.=A0=A0After tha=
t I
suppose it will come down to the first viable use case of sending
application messages over a different transport.

--oren

On Oct 25, 2006, at 12:50 AM, Eranga Samararathna wrote:

      QuickFIX Documentation:
      http://www.quickfixengine.org/quickfix/doc/html/index.html
      QuickFIX Support: http://www.quickfixengine.org/services.html



      Hi,


      How is the quickfix / quickfixj preparation for FIX 5.0? Is quickfix
      need architecture change to address the new loosely coupled FIX
      application layer and FIX session layer?


      BR,


      Eranga


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers





                                                                ***********=
********************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and=20
confidential.
Disclosure to anyone other than the intended recipient is prohibited.
If you are not the intended recipient, please do not disseminate,
distribute or copy this communication, by e-mail or otherwise. Instead,
please notify us immediately by return e-mail(including the original
message with your reply) and then delete and discard all copies of the
message. We have taken precautions to minimize the risk of  transmitting
software viruses but nevertheless advise you to carry out your own
virus checks on any attachment to this message.  We accept
no liability for any loss or damage caused by software viruses.
***************************************************************************=
****