On Thu, Sep 8, 2011 at 11:05 PM, Jos Groot Lipman <[email protected]> wrote:
> ** > A well designed JSON-interface would certainly have made my experiment > easier. > Then keep the ideas coming :). > > One thought: when the interface would rely on GET/POST it might create > cross- > domain problems when used from a web-browser. Therefore my vote goes to > JSON(P) > That's an excellent point which i had completely forgotten about. JSONP should definitely be an option, and i'll be sure to account for that while coding. Note that the so-called Same Origin Policy is going away with HTML5 and XMLHttpRequest2 (the _server_ will decide instead who requests can come from, and publishes that via a new header), which will likely make JSONP a dying technology (since it's just a workaround for the Same Origin Policy). That said, HTML pages are _not_ the only target for a JSON interface. Arbitrary languages can pull JSON for various purposes. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
