Leadtools.Dicom.WCF
Send comments on this topic. | Back to Introduction - All Topics | Help Version 17.5.11.1
| Leadtools.Dicom.WCF Namespace : DICOMService Class |
[AspNetCompatibilityRequirementsAttribute()] [ServiceBehaviorAttribute()] public class DICOMService : IManageService, IObjectRetrieveService, IQueryService, IStoreService
'Declaration <AspNetCompatibilityRequirementsAttribute()> <ServiceBehaviorAttribute()> Public Class DICOMService Implements IManageService, IObjectRetrieveService, IQueryService, IStoreService
'Usage Dim instance As DICOMService
public sealed class DICOMService : IManageService, IObjectRetrieveService, IQueryService, IStoreService
function Leadtools.Dicom.WCF.DICOMService()
[AspNetCompatibilityRequirementsAttribute()] [ServiceBehaviorAttribute()] 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 a 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-ins objects.
For more information about the plug-ins 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
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2