mx::IInterface Class Reference
[Component Interfaces]

The "mother" of all interfaces used for inter-component communications. More...

#include <IInterface.h>

Inheritance diagram for mx::IInterface:

mx::IAsyncAction mx::IAsyncRetrieveCommit mx::ICanUseDialogs mx::ICanUseKeyChain mx::ICanUseTimeouts mx::IComponent mx::ICustomDay mx::IDefWindow mx::IErrorState mx::IExternalAuthenticator mx::IEyeControl mx::IHttpCameraRequest mx::IHttpError mx::IHttpLookupTable mx::IProcessesStream mx::IQtWidget mx::IRequiresActivation mx::IRequiresExternalAuthenticator mx::ISendsMxPEGTiles mx::ISendsSegmentedStream mx::ISendsUndecodedMxPEGFrames mx::IStream mx::ISupportsAsyncStreaming mx::ISupportsCameraSpecification mx::ISupportsEventConfiguration mx::ISupportsFileSpecification mx::ISupportsHostSpecification mx::ISupportsImageConfiguration mx::ISupportsProxySpecification mx::ISupportsPTZControl mx::ISupportsRecordingConfiguration mx::ISupportsRemotePTZ mx::ISupportsSimpleCameraSpecification mx::ISupportsSSLSpecification mx::ISupportsSyncStreaming mx::ISupportsTimetableConfiguration mx::ISupportsWebPageSpecification mx::ITimetableEntry mx::IViewingSession List of all members.

Detailed Description

The "mother" of all interfaces used for inter-component communications.

These interfaces contain nothing but pure virtual methods and are designed to minimize compilation dependencies between MxSDK components. To that end they limit themselves to use in their signatures only trivial data types or those provided by the underlying SDK's system libraries (mxm, mxcpc, ...). Interfaces to GUI components may obviously also use Qt datatypes.

Interface classes

The MxSDK's I* interfaces come in two flavors:

  1. Feature Interfaces describe individual features that a component may or may not have, depending on whether or not it implements the respective interfaces. Among others, we have:
  2. Conceptual Interfaces encode concepts by accumulating feature interfaces and possibly other conceptual interfaces. Example: IHTTPGetStreamSource. Click it to learn which fearture interfaces and other concept iterfaces it inherits (The dashed interface boxes indicate that the interfaces are inherited virtually).

As I* interfaces are by general rule always inherited virtually, that is: using the virtual keyword, concept interfaces are not required to be mutually disjoint.

Author:
[agu] Alexander Gugau

[khe] Kai Hergenroether


The documentation for this class was generated from the following file:
Generated on Fri Jun 29 17:21:05 2007 for MxPEG SDK by  doxygen 1.4.6