Skip to content
New issue

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

Rework - autoping #1333

Closed
DebXWoody opened this issue Apr 26, 2020 · 3 comments
Closed

Rework - autoping #1333

DebXWoody opened this issue Apr 26, 2020 · 3 comments
Assignees
Milestone

Comments

@DebXWoody
Copy link
Contributor

Profanity is doing a lot of thinks during startup. This can take some time. It may happen, that there in a response of autoping to late, because of to much traffic on the road.

@DebXWoody
Copy link
Contributor Author

Example move iq_autoping_timer_cancel(); into src/xmpp/iq.c:_iq_handler

@DebXWoody
Copy link
Contributor Author

Why do you cancel timer on every incoming IQ stanza? When does it suppose to start again?
@mdosch
mdosch 5 days ago Contributor

Every IQ you receive proofs you're connected to the server so they are as good as ping result I guess.
@pasis
pasis 5 days ago Member

I misunderstood the timer semantics. I thought it is always the same timer, but it rather starts on every ping.

I won't insist on waiting for only ping reply. But consider the following when you decide what to push to master: receiving a stanza after sending a ping doesn't mean that the stanza arrived after ping had been sent. The stanza could reside in kernel's buffers. And in this scenario you will need 1 more ping interval to detect broken connection. This is not a big deal for profanity's usecases, so it is up to you to decide how to proceed.

@jubalh
Copy link
Member

jubalh commented May 29, 2020

#1343 got merged.

@jubalh jubalh closed this as completed May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants