> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/es/usando-wiclax/transmision-de-resultados-en-vivo/aplicacion-g-live.md).

# Aplicación G-Live

Un software de cronometraje moderno debería permitir la transmisión en tiempo real de las clasificaciones de eventos a través de múltiples canales. Este es el caso de Wiclax.

En este capítulo, exploraremos cómo mostrar las clasificaciones en vivo o sin conexión. Primero, analizaremos la transmisión en el área de eventos, que llamaremos local, y luego pasaremos a la transmisión por Internet, que llamaremos en línea.

The broadcast of rankings, whether local or online, relies on similar mechanisms but requires a slightly different architecture. We'll be delving into these various points.

To kick things off, we'll explore how to grant access to rankings on any device connected to the same network as the PC hosting Wiclax.

{% hint style="info" %}
We refer to G-live as the part of Wiclax that displays the results. This is a separate web application from the desktop application, which works in direct connection with it.
{% endhint %}


---

# 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.wiclax.com/es/usando-wiclax/transmision-de-resultados-en-vivo/aplicacion-g-live.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.
