On Fri, Mar 2, 2012 at 12:04 AM, Brian Smith <[email protected]> wrote:
> On Thursday, March 1, 2012 at 3:18 AM, Leo Razoumov wrote: > > As a next step, I hope, one can augment limsync with a json API so > > that power users can do more complex things. > > I'm not sure what this would imply. The JSON API is a separate interface, > that IIRC doesn't > have push/pull capabilities yet. > Correct - i don't think we'll be able to do that kind of feature in JSON, largely because JSON doesn't do binary. The closest thing to "commit" i think we'll be able to portably/sensibly pull off is handling embedded docs (but i haven't attempted that yet, and it might or might not be possible with the current internals, but i suspect it is possible). > Ostensibly, any addition of push/pull capabilities should mirror > the existing functionality. > FYI: the JSON API doesn't aim to handle functionality which works directly with a checkout, e.g. checkout, commit, pull, push, update. It's main aim is to provide more or less the same data needed for implementing alternative remote UIs (analog to the HTML interface). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
