You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
First. It would be great to be able to run ping forever. A use-case is the collection of 24-7 logs.
Second. It would be useful to forward the result of a send_ping to another function as soon as it completes (for live plotting, etc...). Something like throwing a yield in the for loop for the executor.run function
Describe alternatives you've considered
I tried calling ping() with count=1, but this has a performance penalty, since this performs DNS query on every ping packet.
The text was updated successfully, but these errors were encountered:
I think having the possibility to yiled is great and we might get to something closer by implementing the async functionality (see #78), which however is more complex to implement than a single yield. For now, we keep this open until we clarify how to go about async.
Regarding the DNS penalty, it is OS-dependant rather than pythonping dependant because we rely on the OS for DNS queries and caching.
Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
First. It would be great to be able to run ping forever. A use-case is the collection of 24-7 logs.
Second. It would be useful to forward the result of a
send_ping
to another function as soon as it completes (for live plotting, etc...). Something like throwing ayield
in thefor loop
for theexecutor.run
functionDescribe alternatives you've considered
I tried calling
ping()
with count=1, but this has a performance penalty, since this performs DNS query on every ping packet.The text was updated successfully, but these errors were encountered: