Uses of Package
biz.onixs.fix.engine

Packages that use biz.onixs.fix.engine
biz.onixs.fix.engine   
biz.onixs.fix.engine.storage   
biz.onixs.fix.engine.transport   
biz.onixs.fix.scheduler   
 

Classes in biz.onixs.fix.engine used by biz.onixs.fix.engine
AbstractOutQueue
           
Engine
          FIX Engine.
Engine.DynamicAcceptorArgs
          Dynamic acceptor event arguments.
Engine.DynamicAcceptorListener
          Dynamic acceptor event listener.
Engine.State
          Engine state.
Engine.StateChangedArgs
          State changed event arguments.
Engine.StateChangedListener
          Engine state changed listener interface.
EngineException
          The exception that is thrown when a non-fatal error occurs in the FIX Engine.
EngineSettings
          The Engine configuration settings.
License
          Base license implementation.
License.Customer
          License customer.
License.Type
          License type.
LicenseException
           
MessageFactory
          Message factory interface.
NumberedRawMsg
           
NumberedRawMsgPool
           
OutQueue
           
Session
          A FIX Session.
It is defined as a bi-directional stream of ordered messages between two parties within a continuous sequence number series.
A single FIX session can exist across multiple sequential (not concurrent) physical connections.
A FIX Connection is comprised of three parts: logon, message exchange, and logout.
A FIX Session is comprised of one or more FIX Connections, meaning that a FIX Session spans multiple logins.
Parties can connect and disconnect multiple times while maintaining a single FIX session.
Session.ErrorArgs
          Error event data.
Session.ErrorListener
          Error event listener.
Session.ErrorReason
          Error reason.
Session.InboundApplicationMessageArgs
          Inbound application-level message received from the counterparty event data.
Session.InboundApplicationMessageListener
          Inbound application-level message received from the counterparty event listener.
Session.InboundSessionMessageArgs
          Inbound session-level message received from the counterparty event data.
Session.InboundSessionMessageListener
          Inbound session-level message received from the counterparty event listener.
Session.MessageEventArgs
          Message related event data.
Session.MessageResendingArgs
          Message resend request received from the counterparty event data.
Session.MessageResendingListener
          Message resend request received from the counterparty event listener.
Session.OutboundApplicationMessageArgs
          Outbound application-level message queued for sending event data.
Session.OutboundApplicationMessageListener
          Outbound application-level message queued for sending event listener.
Session.OutboundSessionMessageArgs
          Outbound session-level message queued for sending event data.
Session.OutboundSessionMessageListener
          Outbound session-level message queued for sending event listener.
Session.StateChangeArgs
          Session state changed event data.
Session.StateChangeListener
          Session state changed event listener.
Session.WarningArgs
          Warning event data.
Session.WarningListener
          Warning event listener.
Session.WarningReason
          Warning reason.
SessionId
           
SessionImpl
           
SessionRole
          SessionInternal role.
SessionState
          Session state.
ThreadRole
          The thread role.
ThreadStartedListener
          Thread started event listener.
 

Classes in biz.onixs.fix.engine used by biz.onixs.fix.engine.storage
EngineException
          The exception that is thrown when a non-fatal error occurs in the FIX Engine.
SessionId
           
 

Classes in biz.onixs.fix.engine used by biz.onixs.fix.engine.transport
SessionImpl
           
SessionManager
           
 

Classes in biz.onixs.fix.engine used by biz.onixs.fix.scheduler
Session
          A FIX Session.
It is defined as a bi-directional stream of ordered messages between two parties within a continuous sequence number series.
A single FIX session can exist across multiple sequential (not concurrent) physical connections.
A FIX Connection is comprised of three parts: logon, message exchange, and logout.
A FIX Session is comprised of one or more FIX Connections, meaning that a FIX Session spans multiple logins.
Parties can connect and disconnect multiple times while maintaining a single FIX session.
 



Copyright © 2005-2012 Onix Solutions. All Rights Reserved.