Hi Derrell,
I filed a bug:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=7170
> We are sending JSONP, which requires JSON, which does not allow that funky
> new Date() stuff that we'd added. Therefore by the "be strict in what you
> send" principle, we should never allow sending that, and flag an error to the
> user who tries to do so. We should never send anything that does not strictly
> conform to the standard.
The principle is right, I also agree on that, but JSONP is already destroying
this due to the callback method. JSONP is javascript and nothing else. It
should be even transferred as text/javascript in contrast to application/json.
To strictly apply the principle, it would need a complete javascript parser to
find the unallowed parts in the server response... this would be by far too
much overkill and cross browser would not be possible... the javascript (JSONP)
would be executed anyway in the script element.
But interesting topic, I'm curious what the core team decides here...
Kind regards
--
Sergio
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
