https://github.com/katyo/tokio_krpc

KRPC implementation in Rust using Tokio
https://github.com/katyo/tokio_krpc

Last synced: 16 days ago
JSON representation

KRPC implementation in Rust using Tokio

• Host: GitHub
• URL: https://github.com/katyo/tokio_krpc
• Owner: katyo
• License: mit
• Created: 2018-01-14T16:51:22.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-01-17T04:43:16.000Z (almost 7 years ago)
• Last Synced: 2024-10-30T16:12:06.547Z (2 months ago)
• Language: Rust
• Size: 13.7 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-MIT

Awesome Lists containing this project

README

        
KRPC protocol in Rust [![Build Status](https://travis-ci.org/katyo/tokio_krpc.svg?branch=master)](https://travis-ci.org/katyo/tokio_krpc)

=====================

Kademlia Remote Procedure Call (KRPC) protocol definition from

[BEP-0005](http://www.bittorrent.org/beps/bep_0005.html):

> The KRPC protocol is a simple RPC mechanism consisting of bencoded dictionaries sent over UDP.

> A single query packet is sent out and a single packet is sent in response. There is no retry.

> There are three message types: query, response, and error.

Implementation notes

--------------------

The API centered around two service interfaces:

1. The service which can be called to make outgoing queries to another nodes.

2. The service which may handle the incoming queries from another nodes.

See DHT ping example here: [tests/dht-bittorrent.rs](tests/dht-bittorrent.rs)

Currently this library developed in single threaded manner to avoid synchronization overhead.