Add web API about rust-ipfs HOT 8 CLOSED

It's how the go and js cli interfaces work. You start the daemon and communicate through the http api. The cli talking to the api is already implemented, we just need to implement the other end.

from rust-ipfs.

Are you suggesting using that library to talk to a local node instead of a remote one?

from rust-ipfs.

Ok, so probably using https://hyper.rs? I see that is also used in rust-ipfs-api

from rust-ipfs.

For reference, this looks like the spec that needs implementing: https://ipfs.docs.apiary.io

from rust-ipfs.

Ok, so probably using https://hyper.rs? I see that is also used in rust-ipfs-api

Or actix-web. They also have actix-web-support. I personally would prefer us using actix-web-server-side, too.

from rust-ipfs.

Or tower-rs. But I don't have a strong opinion.

from rust-ipfs.

warp seems like a good choice for this but may lag behind any tokio 0.2 or std::futures migration. There seems to have been already a gateway server attempt in https://github.com/dvc94ch/rust-ipfs/pull/28 ... I wonder why that one was closed? I understand gateway was probably different from a an http api but the question still stands.

from rust-ipfs.

Work has begin on this using warp and this ticket might now be duplicated by #60 . Should we close this one for now?

from rust-ipfs.