We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It'd be nice if we had a protocol that allowed clients connected to bouncers to synchronise query closes.
DFBnc would need to advertise a capability and then relay new messages between clients that support it.
The text was updated successfully, but these errors were encountered:
I'm thinking some kind of generic message-passing capability may be better.
Sorry, something went wrong.
Yeah, probably. I was thinking about mentioning unread statuses down the line.
Maybe a CLIENTSYNC command that just gets proxied to other clients that support it?
Then we can have CLIENTSYNC CLOSE grebo, CLIENTSYNC READ #foo etc.
CLIENTSYNC CLOSE grebo
CLIENTSYNC READ #foo
On Thu, 7 Apr 2016 at 15:15 Shane Mc Cormack notifications@github.com wrote:
I'm thinking some kind of generic message-passing capability may be better. — You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub #104 (comment)
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub #104 (comment)
No branches or pull requests
It'd be nice if we had a protocol that allowed clients connected to bouncers to synchronise query closes.
DFBnc would need to advertise a capability and then relay new messages between clients that support it.
The text was updated successfully, but these errors were encountered: