ping not happening automatically

[artknight]

As per the docs at ( https://github.com/uNetworking/uWebSockets/blob/master/misc/READMORE.md ) a ping is supposed to happen automatically. The library will autoamtically send pings to clients acording to the idleTimeout specified

However, I am not seeing any pings. Is there something I need to setup?

Note: I am using uWebsockets.js v19.2.0

[hst-m]

I am not seeing any pings

How are you checking for pings? Browser does not show pings. You will get a Pong event on the server

[hst-m]

I am just confused, where did you get idea there is Ping event on browser? You pull that out of no where? Making stuff up as you go?

[artknight]

@hst-m actually I saw it when looking at this lib https://www.npmjs.com/package/ws and I thought that there might be something similar here. Sorry.

[hst-m]

That's where I figured you got it from, obviously those are different things, if you are using Browser websocket you should probably be looking at the Browser websocket API docs https://developer.mozilla.org/en-US/docs/Web/API/WebSocket

[artknight]

@hst-m right, well since that ws lib is able to emit ping events down to clients I naturally thought that uWebsockets.js lib could do the same. That is why I asked the community if there is a way to listen to the pong event in the browser.

No reason to fly off the handle!

[hst-m]

well since that ws lib is able to emit ping events down to clients I naturally thought that uWebsockets.js lib could do the same

I think you are very confused, both libraries send pings to client, this library can do it automatically and manually with ws.ping, but a browser client does not show pings as I tried to tell you many times and you did not listen, the ws library can work as client or server and it is able to show client pings because it is not limited like a browser

[ghost]

If you get pong event on the server then pings do work. The only way to get pong events on the server is if the client sent you a pong. The client will only send a pong if it got a ping.

[artknight]

@hst-m dude since I am not even addressing you, please stay out of this discussion!

[hst-m]

No one wants to waste time with someone so clueless, you don't understand how basic Ping/Pong works

[artknight]

@hst-m yes i am confused because I am not sending any pings from the browser, unless the browser WebSocket automatically sends a ping to the server. If I understand what you are saying correctly the uWebsockets.js lib will keep the websocket open automatically without having me implement anything on the client side?

[artknight]

Btw, @hst-m you are a bully! I hope you lose your privileges to be able to snub anyone else!

[hst-m]

I don't know how many times this needs to be explained to you, in addition to the explanation in the Readme, Server automatically sends Pings to browser, Browser automatically sends Pong responses back to Server. The Browser does not send Ping to Server, it sends Pong which is a response to a Ping. Connection is then kept open. I am expecting to need to explain this at least 3 more times

[artknight]

Thank you.

…

On May 21, 2021 at 8:30 AM, <hst-m ***@***.***)> wrote: > > > well since that ws lib is able to emit ping events down to clients I naturally thought that uWebsockets.js lib could do the same > > I think you are very confused, both libraries send pings to client, this library can do it automatically and manually with ws.ping, but a browser client does not show pings as I tried to tell you many times and you did not listen, the ws library can work as client or server and it is able to show client pings because it is not limited like a browser — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (#530 (reply in thread)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AABGQQQ35MFVESOLSZDMJDLTOZG65ANCNFSM45IMJCWA).