In the Vulcan architecture, the primary elements are the dispatcher,
the engine, the remote access code, services interface, and the server.
The engine, services interface, and remote access are called providers.


The server is an application, albeit a very sophisticated application,
which listens on ports and communicates requests and data across the
wire to the client. It is properly layered on the dispatcher.

The dispatcher is a very thin layer that takes API calls in and
dispatches them to the appropriate provider.

The remote interface is the pair to the server. It passes calls
and data across the wire.

The services interface is just that - the local services interface
that does backups, fixes, etc.

The engine is a multi-threaded piece of code that can be an exclusive
local engine (i.e. embedded) or a multi-instance local engine (i.e.
classic) or a shared resource (i.e. SuperServer). One engine can be
used in any of those configurations depending on the configuration
parameters. There is no difference in the code.

Regards,


Ann