-
Notifications
You must be signed in to change notification settings - Fork 7
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
How do you use this? #2
Comments
Thanks! This is exactly a protocol spec and a parser. It also has two example data types: LWW and RGA. This model was in use in some deployed projects, so I am rather familiar with ins and outs. For a browser-based collaborative editor, the essential parts are:
This year, I may release 4, 1 and probably a bunch of other parsers (Java, C++, etc), depending on circumstances. |
Thank you for the insight. This is rad stuff. :)
…On Mon, Nov 13, 2017 at 7:16 AM Victor Grishchenko ***@***.***> wrote:
Closed #2 <#2>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAAALmYtOIAwuJ8tmVtE64V7ysAhatcCks5s2F1pgaJpZM4QWljv>
.
|
to my poor neck devotedly carrying my heavy head for 38yrs * adjust context semantics: now, only reduced ops use the previous value for every omitted spec UUID; headers, queries and raw ops must reference the previous value *explicitly*; that prevents various inadvertent UUID carry-over bugs e.g. *lww#obj@time1:key=1; @time2:key2=2; should now be spelled as *lww#obj@time1:key=1; *# @time2:key2=2; * put reducer test primers into separate files; those are much easier to edit with vim highlighting * misc small stuff
This looks rad! I’ve read the readme and godoc but there isn’t much showing how to use the library. An example showing a simple text editor or collaborative drawing would be rad. Maybe you already have examples of this in use elsewhere?
The deepdive into the wire protocol and format is awesome though. :)
The text was updated successfully, but these errors were encountered: