Class Hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:

[detail level 12]

▼CSpringCard.PCSC.Bridge.Link.BridgeLink	Abstract communication class between the PC/SC Bridge application (and the driver behind it) and remote reader or a client application implementing the reader-end of the solution
CSpringCard.PCSC.Bridge.Link.BridgeLink.PipeClient	Implementation of a BridgeLink when our end is the client of a named pipe (the other end shall be a PipeServer)
CSpringCard.PCSC.Bridge.Link.BridgeLink.PipeServer	Implementation of a BridgeLink when our end is a named pipe server (the other end shall be a PipeClient)
CSpringCard.PCSC.Bridge.Link.BridgeLink.TcpClient	Implementation of a BridgeLink when our end is the client of a TCP server socket (the other end shall be a TcpServer)
CSpringCard.PCSC.Bridge.Link.BridgeLink.TcpServer	Implementation of a BridgeLink when our end is a TCP server socket (the other end shall be a TcpClient)
▼CSpringCard.PCSC.Bridge.Client.CcidFrame	Implementation of the CCID frames that are exchanged between the PC/SC Bridge (and the driver behind it) and the reader (or virtual reader application)
CSpringCard.PCSC.Bridge.Client.CcidCommand	CCID commands
CSpringCard.PCSC.Bridge.Client.CcidResponse	CCID responses
▼CSpringCard.PCSC.Bridge.Link.BridgeLink.IClient	Interface to be implemented if the link behaves as a client (i.e. our end is the initiator of the connection to the other end)
CSpringCard.PCSC.Bridge.Link.BridgeLink.PipeClient	Implementation of a BridgeLink when our end is the client of a named pipe (the other end shall be a PipeServer)
CSpringCard.PCSC.Bridge.Link.BridgeLink.TcpClient	Implementation of a BridgeLink when our end is the client of a TCP server socket (the other end shall be a TcpServer)
▼CSpringCard.PCSC.Bridge.Link.BridgeLink.IServer	Interface to be implemented if the link behaves as a client (i.e. the other end is the initiator of the connection to ours)
CSpringCard.PCSC.Bridge.Link.BridgeLink.PipeServer	Implementation of a BridgeLink when our end is a named pipe server (the other end shall be a PipeClient)
CSpringCard.PCSC.Bridge.Link.BridgeLink.TcpServer	Implementation of a BridgeLink when our end is a TCP server socket (the other end shall be a TcpClient)
CSpringCard.PCSC.Bridge.Link.Library	DLL control and version
CSpringCard.PCSC.Bridge.Client.Library	DLL control and version
CSpringCard.PCSC.Bridge.Client.ReaderInterface	Reader-side interfaces - To be implemented by the client application
▼CSpringCard.PCSC.Bridge.Client.ReaderNotificationInterface	Interface for the ReaderEngine itself, provided to the client application in ReaderInterface.Enable()
CSpringCard.PCSC.Bridge.Client.ReaderEngine	Engine to run the reader-side of a PC/SC Bridge