# Asynchronous Multi-Protocol

The Asynchronous multi-protocol scenario operates at the network packet layer and expands the reach of the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> from HTTP into other protocols. TCP and UDP packets are supported.

To facilitate this approach a secondary protocol level engine breaks down the packet into elements the main <code class="expression">space.vars.X\_Agent\_Name\_Single</code> can understand. The <code class="expression">space.vars.X\_Agent\_Name\_Single</code> can then modify these elements and the underlying protocol packet will be changed accordingly. The <code class="expression">space.vars.X\_Agent\_Name\_Single</code> is then able to forward the modified package to the designated network endpoint and can even in some instances commence a chat with the endpoint before forming a response packet for the initiating computer. As always, the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> can rely on secondary data sources (APIs, data, other systems) to help form the modified request and response packets.

<figure><img src="https://2423451286-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F42mDa58RoaDxb6t8mbaI%2Fuploads%2Fgit-blob-82ea3f01c9fd6dcdfa0e52bd1a3756d7e21cb515%2Fimage.png?alt=media" alt=""><figcaption><p>Graph</p></figcaption></figure>

Use cases for this scenario includes:

* Database field level security
* ATM stand-in
* SCADA security
* Advanced DNS
* … and many more