Class | Description | |
---|---|---|
ArtDataConnection | ArtDataConnection is an abstract base class. All data providers will implement a derived class of this. The class can be used to read or write any number of streams. This class implements System.IDisposable interface. | |
ArtDocumentDataConnection | This is an abstract base class that represents a connection to a specific document. All data providers would implement a derived class of this. This class implements IDisposable System.IDisposable. | |
ImageDataConnection | ImageDataConnection is an abstract base class. All data providers will implement a derived class of this. The class can be used to read or write any number of streams. This class implements System.IDisposable interface. | |
ImageDataProvider | ImageDataProvider is a base class derived from the System.Configuration.Provider.ProviderBase class ( System.Configuration.Provider.ProviderBase ). It provides a base implementation for the ImageGear image data provider for the PageView and ThumbnailView components. This is an abstract class. | |
ImageDocumentDataConnection | This is an abstract base class that represents a connection to a specific document. All data providers would implement a derived class of this. This class implements IDisposable System.IDisposable. | |
MarkupArtDataConnection | MarkupArtDataConnection is an abstract base class. All data providers will implement a derived class of this. The class can be used to read or write any number of streams. This class implements System.IDisposable interface. | |
MarkupArtDocumentDataConnection | This is an abstract base class that represents a connection to a specific document which supports the Markup Layer API, enabling multiple annotation or art documents to be associated with a single viewable document. All data providers which support the Markup Layer API would implement a derived class of this. This class implements IDisposable System.IDisposable. | |
MarkupArtMiddleware | Markup Middleware provides a simple mechanism by which requests for file operations involving Markup Layers can be intercepted and the data being stored and retrieved can be modified, or the request can be rejected altogether without requiring the Developer to write their own Data Provider from scratch. Middleware can be specified as a property of any Markup Data Provider via Web.config MarkupImageDataProvider. This class contains 4 virtual methods which can be overridden, each of which corresponds to a file operation involving Markup Layers. If a MarkupImageDataProvider is configured to use a derivation of this class, the respective method will be called after each read/list operation, or before each update/create operation. The default implementations of these methods do nothing. | |
MarkupFileArtDataConnection | Internal API. This class derives from MarkupArtDataConnection and implements IEnlistmentNotification. | |
MarkupFileImageDataConnection | Internal API. This class derives from ImageDataconnection and implements IEnlistmentNotification. | |
MarkupFileImageDataProvider | This class derives from the ImageDataProvider. ImageDataProvider This class represents the MarkupFileImageDataProvider. It handles images and art files stored on the file system. Internal API. | |
MarkupFileImageDataProvider.ConfigKeys | Stores the keys used to read properties from Web.config for this ImageDataProvider | |
MarkupFileImageDataProvider.Constants | Stores Constants and Defaults | |
MarkupImageDataConnection | MarkupImageDataConnection is an abstract base class. All data providers will implement a derived class of this. The class can be used to read or write any number of streams. This class implements System.IDisposable interface. | |
MarkupImageDataProvider | ImageDataProvider is a base class derived from the System.Configuration.Provider.ProviderBase class ( System.Configuration.Provider.ProviderBase ). It is an abstract class which forms the foundation of a mechanism by which image/document and annotation data can be requested by the client viewer given a Data Provider Name (optional, can use default data provider), a Document Identifier, and/or a Markup Layer Record ID. Any implementation of a Data Provider must create derivations of all 5 abstract data provider base classes.
The structure of a MarkupImageDataProvider is heirarchical such that a MarkupImageDataProvider derives from Microsoft's ProviderBase and is instantiated from settings specified in Web.confg. Through the OpenImageData() and OpenArtData() methods, the MarkupImageDataProvider opens a MarkupImageDataConnection or MarkupArtDataConnection. This is done so that the connection classes may store contextual information pertinent to that particular provider, ex. (and SQL Data Provider which requires a connection to an SQL database, or an FTP data provider, also requiring a connection). From the connection, a Document Data Connection is opened for a document with a particular identifier. The Document Data Connection classes contain methods that facilitate file operations. Both the Data Connection and Document Data Connection classes implement the IDisposable interface. | |
MarkupImageDataProvider.ConfigKeys | Contains keys used to read settings from Web.config. | |
MarkupImageDocumentDataConnection | This is an abstract base class that represents a connection to a specific document. All data providers would implement a derived class of this. This class implements IDisposable System.IDisposable. | |
MarkupSqlArtDataConnection | This class derives from ArtDataconnection and implements IEnlistmentNotification. Internal API. | |
MarkupSqlImageDataConnection | Internal API. This class derives from ImageDataconnection and implements IEnlistmentNotification. | |
MarkupSqlImageDataProvider | This class embodies an implementation of an SQL Data Provider using the new Markup Layer Interface MarkupImageDataProvider, permitting multiple annotation or art documents to be associated with a viewable document. It retains and respects all of the configuration parameters of SqlImageDataProvider SqlImageDataProvider, and adds a few new parameters which permit it to store and retrieve documents and annotations from separate tables. Subject to user configuration, the intended schema is such that (DocumentIdentifier) is the primary key of a 2-column table (DocumentIdentifier, ImageData) used to store documents, and (DocumentIdentifier, MarkupLayerRecordID) is a composite key used to store annotations in a 4-column table (DocumentIdentifier, MarkupLayerRecordID, ArtData, MarkupLayerName) where DocumentIdentifier is a foreign key referencing the table used to store documents. An example schema is provided. | |
MarkupSqlImageDataProvider.ConfigKeys | Stores the keys used to read properties from Web.config for this MarkupImageDataProvider | |
MarkupSqlImageDataProvider.Constants | Stores Constants and Defaults |