feat: Added HttpClient and updated Persistent client params.

docs/core/clients.md

@@ -11,10 +11,54 @@ import chromadb
 client = chromadb.PersistentClient(path="test")
 ```
 
+`path` parameter must be a local path on the machine where Chroma is running. If the path does not exist, it will be
+created. The path can be relative or absolute. If the path is not specified, the default is `chroma/` in the current
+working directory.
+
 ### Uses of Persistent Client
 
 The persistent client is useful for:
 
 - **Local development**: You can use the persistent client to develop locally and test out ChromaDB.
 - **Embedded applications**: You can use the persistent client to embed ChromaDB in your application. For example, if
-  you are building a web application, you can use the persistent client to store data locally on the server.
+  you are building a web application, you can use the persistent client to store data locally on the server.
+
+## HTTP Client
+
+Chroma also provides HTTP Client, suitable for use in a client-server mode. This client can be used to connect to a
+remote ChromaDB server.
+
+```python
+import chromadb
+
+client = chromadb.HttpClient(host="localhost", port="8000")
+```
+
+HTTP client takes two optional parameters:
+
+- `host`: The host of the remote server. If not specified, the default is `localhost`.
+- `port`: The port of the remote server. If not specified, the default is `8000`.
+- `ssl`: If `True`, the client will use HTTPS. If not specified, the default is `False`.
+
+### Uses of HTTP Client
+
+The HTTP client is ideal for when you want to scale your application or move off of local machine storage. It is
+important to note that there are trade-offs associated with using HTTP client:
+
+- Network latency - The time it takes to send a request to the server and receive a response.
+- Serialization and deserialization overhead - The time it takes to convert data to a format that can be sent over the
+  network and then convert it back to its original format.
+- Security - The data is sent over the network, so it is important to ensure that the connection is secure (we recommend
+  using both HTTPS and authentication).
+- Availability - The server must be available for the client to connect to it.
+- Bandwidth usage - The amount of data sent over the network.
+- Data privacy and compliance - Storing data on a remote server may require compliance with data protection laws and
+  regulations.
+- Difficulty in debugging - Debugging network issues can be more difficult than debugging local issues. The same applies
+  to server-side issues.
+
+### Host parameter special cases
+
+The `host` parameter supports a more advanced syntax than just the hostname. You can specify the whole endpoint ULR (
+without the API paths), e.g. `https://chromadb.example.com:8000/my_server/path/`. This is useful when you want to use a
+reverse proxy or load balancer in front of your ChromaDB server.