| Class Module | Description |
|---|---|
| SecureChildren | The Children Object provides a collection of SecureTCP Objects that have been dynamically created. Each object routes events back to the using application via the SecureServer Control event interface. |
| SecureServer | Use the SecureServer Control to quickly build custom server applications that use authentication and encryption. This control has an internal Daemon object and dynamically creates internal SecureTcp objects as each passive connection is automatically accepted. The SecureServer Control targets high-performance server-side use and consequently relies on non-blocking operation. Applications should only use this control in a non-blocking fashion, as blocking operations (where the SecureTcp object's Timeout property is greater than 0) can cause one session to interfere with others. All events include an object reference as the first parameter so the application can easily reference the SecureTcp object pertaining to the event. |
| SecureTcp | Use the SecureTcp Control to manage streams of data that require security. It simplifies the use of TCP communications by providing methods to establish, send and receive data, and terminate socket-based connections. Client and server authentication, and data encryption / decryption are transparent to the developer. By default, communications will block execution of your program, but you can easily enable non-blocking use for demanding applications that require event-driven communications. You can use this control to implement upper-layer protocols in a secure way, including protocols of your own creation. |
| Enumeration | Description |
|---|---|
| ErrorConstants | Errors are reported to the application with the error object and by firing the Error event. ErrorConstants fall into two classes: design-time errors and run-time errors. The Error event always fires when any error occurs. When Timeout is 0, however, run-time errors are not thrown back to the container. This allows applications that use only non-blocking operation to localize all error handling in the Error event. To summarize: Timeout is 0 (non-blocking). All errors are reported via the Error event. Only errors classified as design time errors are also reported back from methods using the error object. Timeout is not 0 (blocking). All errors are reported via the Error event. All errors occurring within the scope of a method are reported back to the container using the error object. Errors are marked as INFO or FATAL. An INFO error does not affect the State property. A FATAL error performs an Abort and releases all resources. |
| ProtocolConstants | Enumerates values of the Protocol property. |
| ProxyTypeConstants | Proxy Type Constants |
| SecurityConstants | Security Constants |
| StateConstants | TCP State constants |