Skip to content
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.

[🚀] Visible non-query connection to the server #8

Open
MarkL4YG opened this issue May 31, 2019 · 0 comments
Open

[🚀] Visible non-query connection to the server #8

MarkL4YG opened this issue May 31, 2019 · 0 comments
Labels
enhancement New feature or request ui / ux Related to user experience (on the server)

Comments

@MarkL4YG
Copy link
Member

As many users cannot see query connections, it is desirable to automatically establish an additional client connection. This allows users to see and interact with the framework more easily.
All events invoked by this connection should be redirected to the query event dispatching mechanism to avoid parallel data/event flows.
Commands shall not be sent using the voice connection either - as it is supposed to share the same identity, it will show up as the same chat window anyways.

@MarkL4YG MarkL4YG added enhancement New feature or request ui / ux Related to user experience (on the server) labels May 31, 2019
@MarkL4YG MarkL4YG changed the title Visible non-query connection to the server [🚀] Visible non-query connection to the server Jun 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request ui / ux Related to user experience (on the server)
Development

No branches or pull requests

1 participant