> For the complete documentation index, see [llms.txt](https://docs.remede.camarm.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remede.camarm.fr/developers/develop-on-remede/features/dict-client.md).

# DICT Client

Remède supports the DICT protocol and can be used as a DICT client.

Remède is able to communicate with dictionaries servers. The DICT protocol was created in 1997; it has been described in the [RFC2229](https://www.rfc-editor.org/rfc/rfc2229). It is based on TCP/IP.

### How it works

The codebase contains a Dict Client view, which is able to explore dictionaries server.

{% hint style="info" %}
Because Javascript is not able to send TCP requests, we must use native code to send TCP request through sockets. Thanks to [Capacitor Plugins](https://capacitorjs.com/docs/android/custom-code), we can easily call native Java code from our Typescript codebase.
{% endhint %}

<details>

<summary>The Capacitor "TCPClient" plugin</summary>

The plugin native code is located at `app/android/app/src/main/java/dev/camarm/remede/TCPClient.java` and it is defined in the Vue codebase at `app/src/functions/plugins/tcpClient.ts`.

TODO: Not finished

</details>

<details>

<summary>The DICT Client view</summary>

TODO: Not finished

</details>

<details>

<summary>The "Searching using DICT servers" feature</summary>

TODO: Not finished

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.remede.camarm.fr/developers/develop-on-remede/features/dict-client.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.