-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grenache #67
Comments
@allain @bmeck @moperacz @DenisGorbachev @alexeygolev I'd like your opinion especially |
I like what your doing. I've read through the JavaScript side of things and the code reads like you'd expect (well done). I'd like to see more examples of how clients can store arbitrary data in the dht. I'm not really seeing much in the way of security but I suspect that's part of the dht (admittedly I haven't read it all yet). Also, have you given any thought to how you might handle requests made while a peer who could handle it isn't online at the time? It looks like the connect code just returns the first peer it finds, it probably should be at least random. Anyway, this looks good. Do you have a list of things to be done somewhere? Cheers. |
@allain thanks a lot for your feedback Right now the DHT is used only to let clients to discover other clients, but yes, the next step is to add the the grape What I like of this approach is that is really fast, the throughput is incredible higher than pigato and it has less constraints Regarding the security we have several options to think about. I'd like to create a layer on top of Grenache to let Clients publish/fetch encrypted informations using pre-shared keys or asymmetric encryption. Lot to think about. Let's move the discussion here bitfinexcom/grenache#2 |
Hello all
learning from Pigato experience I'm working on a lightweight and really distributed solution that I'd like to present to you all:
https://github.com/bitfinexcom/grenache
My aim is to keep it simple but allow complex constructions and patterns without enforcing the protocol.
What do you think?
The text was updated successfully, but these errors were encountered: