-
Notifications
You must be signed in to change notification settings - Fork 97
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
swarmdb protocol and implementation? #103
Comments
Hi Marcus! |
Hi! I am working with @flanfly on collaborative disassemblers. He is implementing (parts of) RON for Rust right now for panopticon.re, and I am interested in doing a simpler version for 8-bit computers on the web (JS only). We think the ideas behind swarm and RON are amazing, but we are still catching up with you (yesterday, we worked on understanding the spanning tree optimization and the RON representation of the "set" datatype). @flanfly is traveling right now, but a hangout next week (or any other suitable time) would be awesome! |
Hi @gritzko , I would like to know if you will release the source code of the golang version of swarmdb which is in the docker image. |
@lafaucialby Eventually, yes. What is your use case? |
@gritzko I am a university student and I would need to study the code and better understand how it works. |
Is the source code for the olebedev/swarmdb docker image available? Is the server protocol documented? The closest I found is https://github.com/gritzko/swarm-ron-docs/ but that is obviously out of date.
Currently, I am trying to reverse engineer the protocol based on the demo code and the docker black box, but that's quite frustrating.
I understand that there are still challenges to swarm, such as subgraph queries. But I have more trivial questions, too, that could be answered from the implementation of the server. For example, how you key the log entries to make a sortable linear log for the backend db without a version vector. Do you keep a hash to a local timestamp or so?
The text was updated successfully, but these errors were encountered: