I'm (finally!) taking a serious look at making a better version of the
JSON OT type. I'm cross-posting this here because it directly effects
sharejs & derby users, and I think any serious rewrite of wave will
use something like this at the top level to store waves.
I have two questions that I woul
Hi Joseph,
I think that the only sensible option is to delegate the resolution of
this action in the case of conflict back into the application, so some
sort of extension of (4) that allows some arbitrary lambda expression
to be passed as the onconflict method. (Depending on the situation,
they mi
It does complicate the type, and it breaks my nice abstraction. Also
remember that any funny logic will need to be on the server and the
client - and I'd really like the server to be application-agnostic if
possible. That said, the server will probably need
application-specific schema validation &
