Every Socket sends TCP IO events to me. Bytes being received are the most obvious, which are decoded
and some initial validation is performed. Providing it decodes to a fix message the comp id's etc are
used to locate a configured session, if found then the message is handed off to the session actor for
handling.
When a client connects to the server port this class is registered to handle incoming
comms.
It calls the decoder to convert from bytes into a Strongly typed Fix Message.
If the message is badly formed, missing enough header fields and so on this this actor replies
If the session is established, and we know the SfSessionActor to use then the comms is forwarded to it
and it does it all.
Every Socket sends TCP IO events to me. Bytes being received are the most obvious, which are decoded and some initial validation is performed. Providing it decodes to a fix message the comp id's etc are used to locate a configured session, if found then the message is handed off to the session actor for handling.
When a client connects to the server port this class is registered to handle incoming comms.
It calls the decoder to convert from bytes into a Strongly typed Fix Message.
If the message is badly formed, missing enough header fields and so on this this actor replies
If the session is established, and we know the SfSessionActor to use then the comms is forwarded to it and it does it all.
http://doc.akka.io/docs/akka/current/scala/io-tcp.html