Protocol Listeners Overview

These objects configure AlchemyPoint to operate as a server: a WebServer? , MailServer? , ORMQ Provider, etc. Multiple object instances may be specified within a single ServerConfiguration, allowing AlchemyPoint to perform the tasks of several different types of servers simultaneously. This is useful when building APIs or complex services that operate over multiple protocol transports (a service that offers both a HTTP REST and SMTP Mail interface, for example).

AlchemyPoint's ProtocolListeners are comprehensive server implementations conforming to published RFC standards, and are capable of replacing the majority of tasks performed by a typical WebServer? (Apache, lighttpd, etc.) or MailServer? (qmail, sendmail, etc.). These are not "simple" or "light-weight" implementations, but fully-capable server stacks that have undergone heavy testing and development.

Supported Protocol Listeners

HTTP:

• HTTPFullDuplexListener - HTTP Server. Capable of operating as a regular WWW server, a HTTP proxy, binding dynamic services to specific WWW URLs, etc.

SMTP:

• SMTPListener - SMTP Server. Capable of operating as a regular mail server, binding dynamic services to specific e-mail addresses, etc.

ORMQ:

• ORMQSocketListener - Allows an ORMQProvider to service client connections over TCP sockets (useful for allowing connections from remote ORMQ clients).

• ORMQMemListener - Allows an ORMQProvider to service client connections over shared memory streams (useful for allowing local connections from other AlchemyPoint threads within the same server process). This is the fastest ORMQ transport.

• ORMQPipeListener - Allows an ORMQProvider to service client connections over local interprocess pipes (useful for allowing local connections from other system processes running outside the scope of AlchemyPoint Server).