Products | Support | Email a link to this topic. | Send comments on this topic. | Back to Introduction - All Topics | Help Version 19.0.5.5
|
Leadtools.Dicom.WCF Namespace : DICOMService Class |
[ServiceBehaviorAttribute()] [AspNetCompatibilityRequirementsAttribute(AspNetCompatibilityRequirementsMode.Allowed)] public class DICOMService : IManageService, IObjectRetrieveService, IQueryService, IStoreService
'Declaration <ServiceBehaviorAttribute()> <AspNetCompatibilityRequirementsAttribute(AspNetCompatibilityRequirementsMode.Allowed)> Public Class DICOMService Implements IManageService, IObjectRetrieveService, IQueryService, IStoreService
'Usage Dim instance As DICOMService
[ServiceBehaviorAttribute()] [AspNetCompatibilityRequirementsAttribute(AspNetCompatibilityRequirementsMode.Allowed)] public ref class DICOMService : public IManageService, IObjectRetrieveService, IQueryService, IStoreService
The DicomService exposes four contracts to the web clients: IQueryService, IStoreService, IObjectRetrieveService and IManageService
The DicomService is associated with four Endpoints. Each endpoint is a combination of Contract, Address and Binding information. These endpoints can be configured from the configuration file.
Each contract in the DicomService is implemented as a plug-in which is created and loaded dynamically from the configuration file. The DicomService will load the Leadtools.Dicom.Services.DICOMServicesConfigurationHandler section using the name "dicomServicesPluginFactorySection" to create a Leadtools.Dicom.Services.DICOMPluginFactory object which will be used to dynamically create the plug-in objects.
For more information about the plug-in architecture and implementing custom plug-ins see the Server Side Web Service Overview
For more information about the WCF Service security model see WCF Security