Is there a way to close the subscription from the server?

[yaziciahmet]

My confusion is really simple. I have a usecase where it is best to close the subscription or the connection from the server-side. Is this achievable, if so how?

[niklasad1]

Hey @yaziciahmet

I don't understand whether you want to close the just subscription or the entire connection.

1. Closing the subscription is trivial just return early from your subscription callback but you may want to send a special message before do so because the client will never know. See Are clients notified when a subscription task exists? #1223 for further information.
2. Closing the connection is possible but quite complicated to implement where you have to use the low-level server API via middleware/extensions accessible in subscription callback to indicate to close down the connection.

[yaziciahmet]

Hey @niklasad1

I believe what I want is the ability to close the connection. It looks quite complicated to do. Is it planned anytime soon to add some sort of easier access to underlying connection, or maybe just a close functionality can be propagated down somehwo?

[niklasad1]

I prefer not add such thing into the subscription itself but perhaps we could add some builtin middleware to simplify it.
I have to double-check myself whether it's possible to implement...

[yaziciahmet]

Maybe return a tuple from pending.accept()? Subscription itself and a close callback?

[niklasad1]

Hey sorry, for late response but I had a look at this and it's currently possible to add such as thing using extensions in the RPC handler by using the low-level server API example here