good morning!!!!

Skip to content
Snippets Groups Projects
  1. Feb 04, 2019
    • Felix Lange's avatar
      rpc: implement full bi-directional communication (#18471) · 245f3146
      Felix Lange authored
      New APIs added:
      
          client.RegisterName(namespace, service) // makes service available to server
          client.Notify(ctx, method, args...)     // sends a notification
          ClientFromContext(ctx)                  // to get a client in handler method
      
      This is essentially a rewrite of the server-side code. JSON-RPC
      processing code is now the same on both server and client side. Many
      minor issues were fixed in the process and there is a new test suite for
      JSON-RPC spec compliance (and non-compliance in some cases).
      
      List of behavior changes:
      
      - Method handlers are now called with a per-request context instead of a
        per-connection context. The context is canceled right after the method
        returns.
      - Subscription error channels are always closed when the connection
        ends. There is no need to also wait on the Notifier's Closed channel
        to detect whether the subscription has ended.
      - Client now omits "params" instead of sending "params": null when there
        are no arguments to a call. The previous behavior was not compliant
        with the spec. The server still accepts "params": null.
      - Floating point numbers are allowed as "id". The spec doesn't allow
        them, but we handle request "id" as json.RawMessage and guarantee that
        the same number will be sent back.
      - Logging is improved significantly. There is now a message at DEBUG
        level for each RPC call served.
      Unverified
      245f3146
    • Martin Holst Swende's avatar
    • HackyMiner's avatar
      bb7c786b
  2. Feb 03, 2019
  3. Feb 01, 2019
  4. Jan 31, 2019
    • Felix Lange's avatar
      p2p/discover: improve table addition code (#18974) · a89170cf
      Felix Lange authored
      This change clears up confusion around the two ways in which nodes
      can be added to the table.
      
      When a neighbors packet is received as a reply to findnode, the nodes
      contained in the reply are added as 'seen' entries if sufficient space
      is available.
      
      When a ping is received and the endpoint verification has taken place,
      the remote node is added as a 'verified' entry or moved to the front of
      the bucket if present. This also updates the node's IP address and port
      if they have changed.
      Unverified
      a89170cf
  5. Jan 30, 2019
  6. Jan 29, 2019
  7. Jan 28, 2019
  8. Jan 27, 2019
  9. Jan 26, 2019
  10. Jan 25, 2019
  11. Jan 24, 2019
Loading