Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • cert_pk_id
  • proxy_push_result
  • cnode_put_id
  • update-windows-build
  • proxy
  • resubscribe_on_token_change
  • actions
  • client_mode
  • llhttp
  • search_node_add
  • crypto_aes_gcm_argon2
  • ios_notifications
  • log_fmt
  • v2asio
  • fix-msvc
  • message_split
  • meson
  • build_unify
  • pingpush
  • v3.4.0
  • v3.3.1
  • v3.3.1rc1
  • v3.3.1rc2
  • v3.3.0
  • v3.2.0
  • v3.1.11
  • v3.1.10
  • v3.1.9
  • v3.1.8.2
  • v3.1.8.1
  • v3.1.8
  • v3.1.7
  • v3.1.6
  • v3.1.5
  • v3.1.4
  • v3.1.3
  • v3.1.2
  • v3.1
  • v3.0.1
40 results

opendht

  • Clone with SSH
  • Clone with HTTPS
  • Sébastien Blin's avatar
    Sébastien Blin authored
    There is no need to check if the put is ok or not before refreshing it. Indeed,
    the first successful put will make the ok flag to true. But, if an expiration
    is missed (when not connected for example), the put will not be refreshed when
    the connectivity will change (moreover, server and client can have different
    timeouts).
    87041e30
    History
    Name Last commit Last update