Ok,
I'm struggling mainly with the JSONP/Client-side, owhttpd is easy to
understand & all fine..
(although adding commandline-parameters - see below might require some help)
- Now first of all, I'd submit a patch to fix /json outputting valid
JSON-Data. This would change the current behavior i.e.: single elements:
{ "value" : "11.5" }
instead of
" 11.5"
- Error-output: { } or {"error" : "..."} instead of null+partial HTML..
- Add a HTTP-Header (Access-Control-Allow-Origin: *) to enable CORS for
JSON.
This could be a security-risk, but on an already open owhttpd I don't
see any further risk in this case..
If needed, we could also add a commandline-parameter(?) but anybody with
access to owhttpd can read any value anyway without Ajax - so why care..
With CORS working (which is just about this HTTP-Header on server-side!)
JSONP isn't needed anymore (besides IE<10 which I really don't care about)
After, I'll write a summary how to use it; it's very simple but nearly
any doc on the net about JSONP/CORS is only just confusing ;)
Do you prefer the CVS-Diff or a patch-file?
Michael
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
