Mercurial > libervia-backend
view doc/libervia-cli/ping.rst @ 4044:3900626bc100
plugin XEP-0166: refactoring, and various improvments:
- add models for transport and applications handlers and linked data
- split models into separate file
- some type hints
- some documentation comments
- add actions to prepare confirmation, useful to do initial parsing of all contents
- application arg/kwargs and some transport data can be initialised during Jingle
`initiate` call, this is notably useful when a call is made with transport data (this is
the call for A/V calls where codecs and ICE candidate can be specified when starting a
call)
- session data can be specified during Jingle `initiate` call
- new `store_in_session` argument in `_parse_elements`, which can be used to avoid
race-condition when a context element (<decription> or <transport>) is being parsed for
an action while an other action happens (like `transport-info`)
- don't sed `sid` in `transport_elt` during a `transport-info` action anymore in
`build_action`: this is specific to Jingle File Transfer and has been moved there
rel 419
author | Goffi <goffi@goffi.org> |
---|---|
date | Mon, 15 May 2023 16:23:11 +0200 |
parents | c80a0f864b5d |
children |
line wrap: on
line source
========================================= ping: get response time of an XMPP entity ========================================= ``ping`` is more or less the equivalent of the command of the same name on most OSes, but for XMPP. It send a `XEP-0199`_ PING and wait for the answer. When (and if) received, the time to receive the answer is shown, else the time to receive the error message is shown. This can be helpful to quickly test the connection with the server or a device. If you need to get only the response time (without text around), you may use ``-d, --delay-only``. .. _XEP-0199: https://xmpp.org/extensions/xep-0199.html example ------- Get reponse time of a server:: $ li ping example.org