Sending commands to the versioning service

Helix Server applications interact with the versioning service by:

1. Initializing a connection.
2. Sending commands.
3. Closing the connection.

The Helix Server does not maintain any kind of session identifier. The server identifies the sender of commands by its combination of Helix Server user name and client workspace. Different processes that use the same combination of user and workspace are not distinguished by the Helix Server. To prevent processes from interfering with each other when submitting changelists, be sure to use separate client specifications for each process. If you need to create large numbers of processes, consider creating a cache of client specifications and serving them to processes as required.