GithubHelp home page GithubHelp logo

fetchai / ledger Goto Github PK

View Code? Open in Web Editor NEW
76.0 21.0 48.0 36.45 MB

Official Fetch.AI Ledger C++ implementation

Home Page: https://fetch.ai

License: Apache License 2.0

CMake 0.66% Makefile 0.01% Shell 0.02% C++ 95.10% Python 2.72% Jupyter Notebook 1.40% Lex 0.10%

ledger's Introduction

ledger's People

Contributors

alexteslenko avatar baykaner avatar bipll avatar chr15murray avatar cobrascobras avatar daemon63 avatar denis-trapeznikov avatar devjsc avatar ejfitzgerald avatar engineerkatie avatar evsmithx avatar iryna-melnyk avatar jinmannwong avatar jrriehl avatar juanbesa avatar juergend7lytix avatar juliamgomes avatar lrahmani avatar markos avatar missingno57 avatar n-hutton avatar pbukva avatar pierre-wilmot-fetch-ai avatar qati avatar robertdickson avatar saira-mughal avatar talalirfan avatar troelsfr avatar vhavrylov-ncube avatar xiaodongwufetch avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ledger's Issues

Make Nodes multi-node

This initially will be done using the RPC interface, but should also use, or be replaced with the Subscribe interface.

Quite a big task. Ordered goals:

  • Nodes will connect to other Nodes/IP addresses on construction
  • Nodes will forward and filter queries so a query to a node queries all nodes (subject to constraint on number of hops)
  • Nodes will re-organise themselves according to their connection policy

Clean up OEF example

Clean up OEF code so it can go into master or http_server branch:

  • Implementation -> OEFManager
  • Move to /include to indicate this is a new protocol

Pure virtual function called.

Note the incorrect connection to 8080 that causes this.

Ctrl-C to stop
[ 2018-02-06 10:49:44 ] HTTP connection from 127.0.0.1
[ 2018-02-06 10:49:44 ] Client joining with handle 0
[ 2018-02-06 10:49:44 ] Ready to ready HTTP header
[ 2018-02-06 10:49:44 ] Read HTTP header
[ 200 OK ] /node-details, text/html
[ 2018-02-06 10:49:44 ] Client manager did send message to 0
[ 2018-02-06 10:49:44 ] Ready to ready HTTP header
[ 2018-02-06 10:50:06 ] Read HTTP header
Connecting to 127.0.0.1 on port 8080

  • bootstrapping 127.0.0.1 8080
    [ 2018-02-06 10:50:06 ] Adding BeforeStart event listener 4 from thread manager
    [ 2018-02-06 10:50:06 ] Adding BeforeStop event listener 5 from thread manager
    [ 2018-02-06 10:50:06 ] HTTP connection from 127.0.0.1
    [ 2018-02-06 10:50:06 ] Client joining with handle 1
    [ 2018-02-06 10:50:06 ] Ready to ready HTTP header
    [ 2018-02-06 10:50:07 ] Sending message to server
    [ 2018-02-06 10:50:07 ] Start writing message
    [ 2018-02-06 10:50:07 ] Wrote message.
    [ 2018-02-06 10:50:09 ] Connection timed out! 2001 vs. 2000
    [ 2018-02-06 10:50:09 ] Client not repsonding - hanging up!
    [ 2018-02-06 10:50:09 ] Removing event listener 4 from thread manager
    [ 2018-02-06 10:50:09 ] Erasing BeforeStart.
    [ 2018-02-06 10:50:09 ] Done removing event listener 4 from thread manager
    [ 2018-02-06 10:50:09 ] Removing event listener 5 from thread manager
    [ 2018-02-06 10:50:09 ] Erasing BeforeStop.
    [ 2018-02-06 10:50:09 ] Done removing event listener 5 from thread manager
    [ 2018-02-06 10:50:09 ] Reading header failed, closing connection.
    libc++abi.dylib: Pure virtual function called!
    Abort trap: 6

Add RPC/Subscription interface request

It might be interesting if there were a way for a hopeful client to inspect the API of a node, perhaps as a set of function definitions, so it would be possible for a client to inspect and use the RPC interface of a node without prior knowledge

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.