The C++ framework for developing highly scalable, high performance servers on Windows platforms.

IAcceptStreamSocketConnectionFilters Class Reference
[Stream SocketsInterfacesFilteringProtected destructors on abstract base classes]

Inheritance diagram for IAcceptStreamSocketConnectionFilters:
Collaboration diagram for IAcceptStreamSocketConnectionFilters:

List of all members.


Detailed Description

This interface works in conjunction with IFilterStreamSocketConnections and allows stream filters to be added to a class that can use them.

Public Member Functions

virtual void AddConnectionFilter (IFilterStreamSocketConnections &filter, bool canGenerateOurOwnWrites)=0
 Adds a connection filter to the connection manager. Connection filters are called in order to process calls with requests being called from "top to bottom" and completions being called from "bottom to top". For example, if filter A is added and then filter B is added and then we make a write request the data would be processed first by filter B and then by filter A (user -> B -> A -> wire). When a read completes.
virtual
IIndexedOpaqueUserData::UserDataIndex 
RequestUserDataSlot (const _tstring &name)=0
 Request a named user data slot and get an index to use in calls to methods on IIndexedOpaqueUserData.
virtual
IIndexedOpaqueUserData::UserDataIndex 
LockUserDataSlots ()=0
 Prevent more user data slots from being allocated. Returns the number of user data slots that have been allocated.

Protected Member Functions

virtual ~IAcceptStreamSocketConnectionFilters ()
 We never delete instances of this interface; you must manage the lifetime of the class that implements it.

Constructor & Destructor Documentation

virtual ~IAcceptStreamSocketConnectionFilters (  )  [protected, virtual]

We never delete instances of this interface; you must manage the lifetime of the class that implements it.


Member Function Documentation

virtual void AddConnectionFilter ( IFilterStreamSocketConnections filter,
bool  canGenerateOurOwnWrites 
) [pure virtual]

Adds a connection filter to the connection manager. Connection filters are called in order to process calls with requests being called from "top to bottom" and completions being called from "bottom to top". For example, if filter A is added and then filter B is added and then we make a write request the data would be processed first by filter B and then by filter A (user -> B -> A -> wire). When a read completes.

(wire -> A -> B -> user).

Implemented in CFilteringStreamSocketConnectionManagerBase.


Generated on Sun Sep 12 19:10:13 2021 for The Server Framework - v7.4 by doxygen 1.5.3