PHP's json conversions have

Shaggy — Mon, 15 Mar 2010 13:40:16 +0000

PHP's json conversions have benchmarked' out to be faster than serialize/unserialize - which all the cool kids are using these days... Premature optimization - finding the resource pinch before it exists - is quite difficult. Do the best you can to build that application - optimisation is far easier when you have the complete picture to look at.

That thing you figure may be the resource hog at the start often turns out to be 5% of your execution time while that innocuous process waaayy back there in your code - you know, that simple one - silently eats 40%.

Cheers,
Shaggy.

It much depends on how

jeevesbond — Sat, 13 Mar 2010 00:53:00 +0000

It much depends on how efficient the algorith doing the conversion is. If you're looking to get really technical, use Big O notation to work it out.

Personally, I would leave your script how it is, as long as it isn't causing any performance problems.

I would test it though, by feeding the PHP script lots of large XML responses (just create a PHP script that pretends to be like the Web service your script is requesting data from). Use the time() function to see how long it takes to process large amounts of data and whether the server becomes too overloaded.

Frankly, I doubt you'll have any problems. I would also imagine that using JSON would be marginally faster since it is Javascript.

I realise that JavaScript can

benf — Fri, 12 Mar 2010 17:32:58 +0000

I realise that JavaScript can handle XML but as I see things, it appears to be more efficient with JSON than XML?

Do you think it would actually be more efficient just handling the XML directly than trying to convert to JSON?

When you're making an extra

avido — Wed, 10 Mar 2010 14:45:25 +0000

When you're making an extra step there are always performance issues.

I don't really see why you want to encode the xml to json since javascript also can handle xml