Plan a Windows client connection ​

Begin with the documented Coordinator DB installation path rather than assuming a Windows installer or service package exists. The installation guide describes installing the latest release and starting it with existing XML configuration files. It does not promise a separate Windows desktop distribution.

For a Windows application that needs to query an already running server, HTTP provides a language-neutral request interface. Configure an authenticated request to POST /, select the managed database and send SQL in the request body. Choose a registered output format the application can decode. Validate with a small SELECT before sending real input.

Keep the server address, native TCP port and HTTP port distinct. The sample uses native port 7400 and HTTP port 7401, bound for local access. A client on another machine needs the intended network reachability and secure transport; changing its operating system does not change those requirements.

Server-side file() access currently requires Unix and reads beneath a configured root. For data on the client machine, use a documented upload or native-client input workflow instead of assuming the server can read a Windows path.

See installation, HTTP and file sources.