Native JSON in IE8

Native JSON in IE8 : EasyCoded

Native JSON in IE8 : EasyCoded — Wed, 10 Sep 2008 21:24:50 GMT

PingBack from http://www.easycoded.com/native-json-in-ie8/

re: Native JSON in IE8

steve — Wed, 10 Sep 2008 23:26:43 GMT

All very cool, but what happens when "naughty" JSON is encountered?

Is an empty object returned?

An error object returned?

null returned?

Is the "offending" bit removed?

As a developer, if something went wrong, I want to know about it. How do I find out what didn't work? or do I?

re: Native JSON in IE8

Tino Zijdel — Thu, 11 Sep 2008 02:55:29 GMT

Does this interface also require UTF8 encoded input as per RFC4627 (which is a silly requirement imo)?

re: Native JSON in IE8

Paul — Thu, 11 Sep 2008 05:24:20 GMT

> If the reviver returns null, the object member is deleted.

You mean undefined, correct? The latest spec says "If it returns undefined then the member is deleted from the result."

re: Native JSON in IE8

JackyMao — Thu, 11 Sep 2008 06:24:18 GMT

Very Nice!

Obviousely, the Native JSON will make things run much more quickly! as Oliver (http://blogs.msdn.com/ie/archive/2008/09/09/what-s-new-for-jscript-for-ie8-beta-2.aspx#8939732) expect.

& Hope IE 8 can be more safe on every progress he make!

re: Native JSON in IE8

ERP Software Systems, WEB Sites Development and Design — Thu, 11 Sep 2008 10:23:11 GMT

I love AJAX. I think that what Microsoft has done is very useful. Just must be tested and to re-write the source code.

Common Sense

wageslave — Thu, 11 Sep 2008 12:15:21 GMT

Whatever happened to common sense when naming functions? How about JSON.encode() and JSON.decode()?

wtf is stringify?

Supporto nativo JSON in Internet Explorer 8

Pietro Brambati Blog — Thu, 11 Sep 2008 15:00:58 GMT

Uno dei post che ho letto con più interesse sul blog del team di prodotto riguarda il supporto nativo

re: Native JSON in IE8

Gordon — Thu, 11 Sep 2008 16:11:10 GMT

What the !@#$! .stringify();???

Was JSON.serialize(JSONObj, replaceHandler, delimiter);

not available?

You guys come up with some of the weirdest APIs I've ever seen.

Gordon

re: Native JSON in IE8

Ted — Thu, 11 Sep 2008 16:26:21 GMT

Gordon: "stringify" is a standard; it's not Microsoft's name.

re: Native JSON in IE8

Neil Garb — Thu, 11 Sep 2008 16:33:53 GMT

Why are we moving away from evalJson() ?

re: Native JSON in IE8

EricLaw [MSFT] — Thu, 11 Sep 2008 22:49:39 GMT

@Neil, @Gordon-- Different frameworks have different names for the functions. The names selected for IE's native implementation are based by the ES3.1 proposal, which is in turn based on the most popular/definitive implementation, Douglas Crockford's json2.js.

@Tino: RFC4627 covers the wire format for the application/json media type. It's not applicable in this case because the script engine isn't working with a wire format/media type, it's working with a Unicode string. Internally, IE (and I'd imagine most browsers) decode from wire formats into Unicode (UTF16 in our case) and then convert back into encoded formats only as needed. Therefore, your server needs only to return a string in some encoding with the proper encoding specified, then XMLHTTPRequest or XDomainRequest (or whatever) will convert that string into Unicode, and that Unicode string will be handled by the parse() method.

re: Native JSON in IE8

cbarsan — Fri, 12 Sep 2008 21:18:12 GMT

@steve:” what happens when "naughty" JSON is encountered?”. -- A: If your code doesn’t define the JSON object, a reference to JSON returns the builtin JSON object. You might have a problem only if your code relies on JSON being undefined. If your code defines the JSON object, most probably you override it and you have no problem. If you define your own JSON object conditionally like “if(!this.JSON){ JSON=…}” then the builtin JSON object is visible in your code. An expression like “JSON.encode()” might fail because the builtin object doesn’t have the function “encode”.

@paul – right, it is undefined.

re: Native JSON in IE8

Mitch 74 — Mon, 15 Sep 2008 18:19:16 GMT

before someone else asks: why won't the IE team look at how other browsers store wire formats? Gecko and KHTML/Webkit are open!

Answer: there would be a risk that looking at these code may lead to some form of copyright infringement.

Suggestion: why not ask in Gecko and/or Webkit mailing lists how these browsers encode it?

Question: UTF16 (2 bytes per character) is a bit... wasteful, isn't it? At the same time, as far as I know, it doesn't cover all characters.

Other question: what now happens on UTF-8 encoded documents that get the MS non-standard UTF8 prologue (reversed question mark etc.) ? This may actually cause trouble here if the stream was originally such a document.

JScript and Developer Tools in IE8 Beta 2

Notes about JScript — Thu, 18 Sep 2008 21:00:17 GMT

As you might be aware that Internet Explorer Beta 2 was released few weeks back. In this JScript team

Native JSON in Internet Explorer 8

DotNetKicks.com — Mon, 06 Oct 2008 11:33:35 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Silverlight Crossdomain Access Workarounds

Jon Galloway — Sat, 13 Dec 2008 01:42:22 GMT

I was testing out some typography with Silverlight and figured I’d try grab some text from Wikipedia

Responding to Change: Updated Getter/Setter Syntax in IE8 RC 1

IEBlog — Wed, 14 Jan 2009 00:17:26 GMT

As a Program Manager, I love to write feature specifications (that’s a job description requirement)!

Responding to Change: Updated Getter/Setter Syntax in IE8 RC 1

Блог команды разработчиков Internet Explorer 8 — Sun, 25 Jan 2009 23:22:29 GMT

Обновленный синтаксис Getters/Setters в IE8 RC1 Как программному менеджеру, мне нравится писать спецификации

Site Compatibility and IE8

IEBlog — Fri, 13 Mar 2009 04:59:15 GMT

Reports of broken sites are an important part of the feedback the IE team receives from the community.

Internet Explorer 8 의 네이티브 JSON

IE8 팀 블로그 — Tue, 17 Mar 2009 11:17:25 GMT

    이 글의 제목을 보고 아셨을지 모르겠지만, Internet Explorer 8 은 Beta 2에서 네이티브 JSON 구문해석기능과 serialization

What’s new in JScript for IE8

IEBlog — Wed, 25 Mar 2009 02:28:06 GMT

During Beta1 and Beta2 pre-releases of IE8, we’ve blogged about the performance optimizations done in

What’s new in JScript for IE8

JScript Blog — Wed, 25 Mar 2009 05:58:49 GMT

During Beta1 and Beta2 pre-releases of IE8, we’ve blogged about the performance optimizations done in

A Major Milestone in JavaScript Standardization

JScript Blog — Thu, 09 Apr 2009 20:40:39 GMT

In the world of web standards, JavaScript is known as ECMAScript and maintenance of its definition is

Native JSON in IE8, Firefox 3.5 plus Json.NET

James Newton-King — Sun, 12 Apr 2009 15:32:51 GMT

Native JSON parsing and serialization is a new feature to IE8 and Firefox 3.5 and makes evaling a thing

Versioning Language Features in JScript

JScript Blog — Fri, 17 Apr 2009 02:12:28 GMT

With Internet Explorer 8 we introduced several new JScript language features including native JSON support

Resources for my talk on the Microsoft Web Platform and Internet Explorer 8

Pla.NET Southeast! — Fri, 08 May 2009 17:49:05 GMT

I had a great time this week speaking to the Atlanta PHP user group about our new Web Platform gallery