Returns the connection timestamp that was registered the first time the client established a connection with the build server.

Gets a unique classes directory to store classes and any kind of compilation products. This classes directory can be freely accessed and managed by the client without any further intervention except its deletion when the client exits.

Returns true if the client is currently connected to the server, otherwise false. This entrypoint is important for debugging purposes and managing some state related to BSP clients.

Tells the caller whether this client manages its own client classes directories or whether bloop should take care of any created resources.

Selects the parent root directory where all client classes directories will be created. The root classes directory can be derived from either the project or a classes directory specified by the bsp client in its initialization handshake. The semantics for the management of these directories change depending on how the root dir for client classes directories is derived.

If bloop uses the parent of the generic classes directory as the root of all client classes directories, then it also manages its contents and can remove these classes directories as it sees fits (typically after the client shuts down the connection). A managed directory is always created inside a project-specific directory so internal directories can use a format directory that already assumes the project id.

Else, if the client passes its own root classes directory, then Bloop only creates new directories but it doesn't remove them at all and instead leaves the management of the contents of these directories to the client. Bloop will still write compilation products in the client directories when a client compile happens, but it's the responsibility of the client to remove them from disk. An unmanaged directory is global and it must contain classes directories for every project/build target in such a way that there's no clash among them.