Disconnected clients

[Yuriy]

Hi,
I'm trying to use Goliath as a streaming server. How can I detect
disconnected clients to stop streaming to them?
Using on_close works if clients are connected directly to Goliath but
it seems not working if I run Goliath on Heroku.

Thanks,
Yuriy.

[Ilya Grigorik]

Umm, that should work. If it doesn't, I'd consider that to be a pretty serious bug for Heroku.. If the upstream client closes the connection, that should be propagated back to your server.

Have you tried contacting the Heroku team?

ig

[Yuriy]

This is a reply I just got from Heroku:

"Unfortunately, our load balancers automatically keep a pool of TCP
connections open to their backends (in this case, the Heroku routing
layer). When a client connection closes, the load balancer doesn't
close the connection to its backend, and therefore, neither our
routing layer nor the web process running on the dyno are aware of
this event.

We're not pleased with this solution but unfortunately we've yet to
come up with a work-around."

Sound like I'm out of luck. Any alternatives?

Thanks,
Yuriy.

[Ilya Grigorik]

Umm, well that's a pretty nice fail. That means any sort of streaming use case on Heroku is broken. Can they propagate any sort of notification?

ig

[Matt Aimonetti]

I forwarded this thread to Ryan Daigle since that was the whole point they changed their infrastructure and got rid of varnish. Yuriy did you try to run your code on Cedar by any chance?

- Matt

[Yuriy]

Yes, I run it on Cedar

Yuriy.

On Aug 15, 2:54 pm, Matt Aimonetti <mattaimone...@gmail.com> wrote:
> I forwarded this thread to Ryan Daigle since that was the whole point they changed their infrastructure and got rid of varnish. Yuriy did you try to run your code on Cedar by any chance?
>
> - Matt
>

[Oded Argon]

Hi,

I just stumbled upon the same problem I think.

Do any of you have any new information about this issue?

Oded.

[Ernest Surudo]

Ditto, two years later. I haven't tried it yet, but I guess I will find out soon...