> - 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"
I'd opt for
[ " 11.5" ]
(unnamed array) for single values..
The change is really trivial, just add [] - any other opinions?
> - Error-output: { } or {"error" : "..."} instead of null+partial HTML..
This isn't trivial, on the first request I get what I expect, on the
second++ a full HTML-answer?
This would be really important for a useful error-handling in Ajax-clients..
> - Add a HTTP-Header (Access-Control-Allow-Origin: *) to enable CORS for
> JSON.
Overall: this works really great! 100x faster/less resource-usage than
anything else which might also be a big benefit for any visualisation of
owfs-data..
There is only one drawback: no IE below v10!
FF, Chrome(Webkit), Safari(Webkit), Opera, Dolphin, ... are all fine
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
