0
I Use This!
Inactive

Commits : Listings

Analyzed 2 days ago. based on code collected 2 days ago.
Oct 29, 2025 — Oct 29, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Switch to newer version of sockjs More... almost 14 years ago
Bump version and update dependencies More... over 14 years ago
Make server-side logging work the same as client More... over 14 years ago
Objects that we write to don't actually need to record the object version at all: only reads need validating for versions. More... over 14 years ago
Accomodate movement of Map from cereal to atomize-client. Now that cereal can encode undefined we can drop explicit encoding support for that from the atomize protocol. A few other tidyups, bump version and dependencies, release. More... over 14 years ago
Bump version and release. More... over 14 years ago
JSON can't represent 'undefined' values, so work around that. More... over 14 years ago
Oops. Correct license date More... over 14 years ago
Supply default to cope with missing path. Bump and release More... over 14 years ago
Large version bump only, and release More... over 14 years ago
Given protocol change, bump version and release. More... over 14 years ago
No need to distinguish txn response types, and no doing so leads to much simpler client code. More... over 14 years ago
Make server robust-er to misbehaving clients More... over 14 years ago
Minor changes and improvements More... over 14 years ago
This might just be enough to implement security models. More... over 14 years ago
Whoops, forgot to save More... over 14 years ago
Add keywords, bump version, release More... over 14 years ago
Make it even lazier. Also, now that the client initial root is version 0 and unpopulated, no longer need 2 bumps on the server initial root. More... over 14 years ago
When sending new objects down to clients, don't send down the fields of those objects. Instead, send down the object at version 0, and rely on the client to issue a retry with a read of said object if it needs to. Thus we get lazy-expansion of the objects each client knows about: in particular, we don't need to start by sending down the entire object graph. More... over 14 years ago
Bump version and release More... over 14 years ago
Minor performance improvements More... over 14 years ago
Saner variable names More... over 14 years ago
Hopefully, a complete fix for this problem. More... over 14 years ago
Make each TVar track the last txnSet that wrote to it, and use this when calculating updates to clients. This eliminates the possibility that a client is sent updates which represent a subset of a committed txn and is able to observe different TVars before and after said txn More... over 14 years ago
Minor bug fix to ensure version = 1 on createds grabbed during retry More... over 14 years ago
Bump version and release More... over 14 years ago
Turns out we really do to capture creations on retry because the same client could, whilst retrying, use the created obj in another txn, and so we need to make sure the server knows about it when it first shows up. More... over 14 years ago
Efficiency: keep track of the last vsn of a tvar that we send each client. Then use this to avoid sending the same client multiple updates to the same tvar vsn. More... over 14 years ago
More docs; consistency; remove redundant arg More... over 14 years ago
Some docs; some abstraction More... over 14 years ago