JSON - Revision history

Brandon CS Sanders at 16:58, 3 April 2008

2008-04-03T16:58:36Z

Brandon CS Sanders at 16:39, 3 April 2008

2008-04-03T16:39:51Z

Brandon CS Sanders: /* YAML instead of JSON */

2008-04-03T16:38:13Z

‎YAML instead of JSON

Brandon CS Sanders: /* JSON instead of YAML */

2008-04-03T16:37:52Z

‎JSON instead of YAML

Brandon CS Sanders at 16:37, 3 April 2008

2008-04-03T16:37:22Z

Brandon CS Sanders at 16:36, 3 April 2008

2008-04-03T16:36:43Z

Brandon CS Sanders: /* JSON instead of YAML */

2008-04-03T16:34:42Z

‎JSON instead of YAML

Brandon CS Sanders: /* YAML instead of JSON */

2008-04-03T16:33:58Z

‎YAML instead of JSON

Brandon CS Sanders: /* JSON instead of YAML */

2008-04-03T16:27:56Z

‎JSON instead of YAML

Brandon CS Sanders at 16:26, 3 April 2008

2008-04-03T16:26:59Z

@@ Line 10: / Line 10: @@
 :* The browser can instantiate objects using eval (very fast) without any server side translations
 :* We're already using JSON in a number of places
 '''Cons: Requires work in Ruby and Rails'''
@@ Line 26: / Line 27: @@
 :* YAML must be converted to JSON before sending to the browser
 :* Must rewrite everywhere we've already serialized

← Older revision		Revision as of 16:39, 3 April 2008
Line 1:		Line 1:
−	[[JSON]] is a ~~data-oriented~~ subset of Javascript. See http://www.json.org/ for specification.	+	[[JSON]] is a subset of Javascript that is specifically for data exchange. See http://www.json.org/ for the specification.

	== Relationship with [[YAML]] ==		== Relationship with [[YAML]] ==

@@ Line 19: / Line 19: @@
 == YAML instead of JSON ==
 '''Pros: Rails Compatibility, Ruby Compatibility'''
-** ActiveRecord makes serialized database fields work transparently
+:* ActiveRecord makes serialized database fields work transparently
-** The differences between symbols and strings in hashes are preserved
+:* The differences between symbols and strings in hashes are preserved
-** Can transparently replace our current use of serialize
+:* Can transparently replace our current use of serialize
 '''Cons: Requires work in Javascript, Must convert existing code'''
-** YAML must be converted to JSON before sending to the browser
+:* YAML must be converted to JSON before sending to the browser
-** Must rewrite everywhere we've already serialized
+:* Must rewrite everywhere we've already serialized

@@ Line 8: / Line 8: @@
 == JSON instead of YAML ==
 '''Pros: Javascript Compatibility'''
-** The browser can instantiate objects using eval (very fast) without any server side translations
+:* The browser can instantiate objects using eval (very fast) without any server side translations
-** We're already using JSON in a number of places
+:* We're already using JSON in a number of places
 '''Cons: Requires work in Ruby and Rails'''
-** We have to handle serialization to/from the database ourselves (rather than rails doing it for us)
+:* We have to handle serialization to/from the database ourselves (rather than rails doing it for us)
-** Doesn't support loopy data structures
+:* Doesn't support loopy data structures
-** Doesn't encode the classes of objects
+:* Doesn't encode the classes of objects
-** Only allows string keys
+:* Only allows string keys
 == YAML instead of JSON ==

@@ Line 8: / Line 8: @@
 == JSON instead of YAML ==
 '''Pros: Javascript Compatibility'''
-* The browser can instantiate objects using eval (very fast) without any server side translations
+** The browser can instantiate objects using eval (very fast) without any server side translations
-* We're already using JSON in a number of places
+** We're already using JSON in a number of places
 '''Cons: Requires work in Ruby and Rails'''
-* We have to handle serialization to/from the database ourselves (rather than rails doing it for us)
+** We have to handle serialization to/from the database ourselves (rather than rails doing it for us)
-* Doesn't support loopy data structures
+** Doesn't support loopy data structures
-* Doesn't encode the classes of objects
+** Doesn't encode the classes of objects
-* Only allows string keys
+** Only allows string keys
 == YAML instead of JSON ==
 '''Pros: Rails Compatibility, Ruby Compatibility'''
-* ActiveRecord makes serialized database fields work transparently
+** ActiveRecord makes serialized database fields work transparently
-* The differences between symbols and strings in hashes are preserved
+** The differences between symbols and strings in hashes are preserved
-* Can transparently replace our current use of serialize
+** Can transparently replace our current use of serialize
 '''Cons: Requires work in Javascript, Must convert existing code'''
-* YAML must be converted to JSON before sending to the browser
+** YAML must be converted to JSON before sending to the browser
-* Must rewrite everywhere we've already serialized
+** Must rewrite everywhere we've already serialized