<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16496"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial>in practice the most people from trading desk don't will learn
this tags and if the are some problems and you must tell what was happen, you
have to convert the fix messages, so they can understand
them.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial>Max, you are right lists can be slower, but they are fast
enough to convert more as 5000 per sec on single core. FIX self is very very
slower - in our produktion sessions I have seen max 1000 messages per sec.
If you have to work with fix messages in your erlang applikation ( compute
some values or specify some logic etc ), you must convert messages to
records or list and the values to numbers or atoms and so on.
</FONT></SPAN><SPAN class=070312207-10102013><FONT color=#0000ff size=2
face=Arial>Yes if you write the fix engine, that acts as hub, you don't need to
do it all and can work with binaries. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial>You are right my projects on github are just prototypes and
not fit for production , but if I have to do it for produktion purpose, i would
do it in the same way.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=070312207-10102013><FONT color=#0000ff
size=2 face=Arial>Maxim</FONT></SPAN></DIV></BODY></HTML>