SfSessOutEventRouterImpl
Related Doc:
package session
Something has happened in the session layer to say lets close the socket now
Something has happened in the session layer to say lets close the socket now
If a client connects to a server, the router is connected and attached to the sessionactor based on the sessionId - ie fielde from the message header.
If a client connects to a server, the router is connected and attached to the sessionactor based on the sessionId - ie fielde from the message header. If another client then spams in a connection while one is created, then you can have several routers linked to a single SessionActor. So the session actor has to confirm that the router it is working with matches the sender of any tcp events from the SfSocketHandlerActor
If an actor fails then the actor ref will fail. But I dont mind as if the tcp actor fails the socket is gone anyway.
true if it matches
The session closed
The session closed
The session opened
The session opened
We received a fix message, validated it, confirmed it was not a session message and so now need to forward it to the business OMS
We received a fix message, validated it, confirmed it was not a session message and so now need to forward it to the business OMS
The decoded business message
Under any normal conditions there should be zero rejects.
Under any normal conditions there should be zero rejects. So, decide what you want to do...
- the body will be a reject ie fixMsg.body match{ case rj:RejectMessage => }
Obviously the logging could go someplace eles, BUT this is so damn handy for testing.
Obviously the logging could go someplace eles, BUT this is so damn handy for testing. Originally this sent the message, but since I want an Ack I could got get the implicit sender to be assigned, which means the ack never came back