[wp-trac] [WordPress Trac] #23753: Switch to JSON encoding instead of PHP serialisation

[WordPress Trac]

#23753: Switch to JSON encoding instead of PHP serialisation
-----------------------------+------------------------------
 Reporter:  sanchothefat     |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Database         |     Version:  trunk
 Severity:  minor            |  Resolution:
 Keywords:  dev-feedback     |
-----------------------------+------------------------------

Comment (by johnbillion):

 This doesn't make a lot of sense. Serialization serves to store data in
 its current state, allowing you to retrieve it later. JSON is not capable
 of doing this (as noted in your 'Cons' above).

 If the current serialization method breaks with multibyte characters then
 we should fix the serialization, not change it to JSON. Could you provide
 an example which breaks the serialization? I'd like to see it and find out
 why it breaks.

 The only real benefit I see in your list of 'Pros' is number 2 (the
 subject of which has been debated extensively on wp-hackers, IRC, etc) and
 is more easily solved by developer education.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23753#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software