Contains classes and data for making calls to SOLO Server web services.
Base implementation for web form calls, including things like posting data to the trial tracking service, making previous-generation (Automation Client) calls, etc...
The base/abstract class from which all WebServiceCall implementations are derived. Key functions of this class include:
- Signing and encrypting web service requests.
- Decrypting and verifying web service responses.
- Validation of session codes (to prevent replay attacks).
- Providing a common means in which web service requests may be generated and responses may be processed, regardless of whether or not direct Internet connectivity is being used.
Web services presently implemented include:
|XmlActivationService||Includes methods for Electronic License Activation, status checking, and deactivation.|
|XmlLicenseFileService||Used for retrieving and refreshing License Files electronically.|
|XmlLicenseService||Used for retrieving and sending license data (such as checks for product updates, customer registration, etc...).|
|XmlNetworkFloatingService||Used for SOLO Server-based Network Floating licensing implementations. This allows limiting the number
of concurrent users/open sessions, status checking, closing sessions, and provides a means to "check-out" sessions for
off-line use (when allowed) and to "check-in" any checked-out sessions when off-line use is no longer required.
By default, the .NET Framework sets the user-agent in the HTTP header to "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol x.x.x.x)" where x.x.x.x is the version of the common language runtime.
It is possible to specify the user-agent value when using the web service references by modifying the
HttpWebClientProtocol.UserAgent property .