I notice a todo referring to when solr 1.3 is released... about solr-php-client

[GoogleCodeExporter]

The simple answer: I haven't removed the todo because I haven't made a decision 
yet.

In my own testing I've found that serialized PHP is faster to parse than JSON, 
yes, but unlike the JSON output 
writer I can't control how named lists are handled nor can I make it map to 
standard class instances like I can 
with json_decode - So to maintain the current client API I haven't moved 
forward with using the serialized php 
output writer. My fear would be that the small difference in parse time would 
be outweighed by the extra 
work we'd have to do on the client side to produce the same output. 
Additionally, there have been bugs with 
outputting the proper string lengths in the serialization format when not using 
utf-8 encodings in all your 
data. 

Issue #3 is also related to your question.

Original comment by [email protected] on 16 Apr 2009 at 3:26

[GoogleCodeExporter]

I've removed the related TODO's and decided to stick with JSON response writer. 
See r16

Original comment by [email protected] on 4 Aug 2009 at 6:24

• Changed state: Fixed

[GoogleCodeExporter]

Really glad to hear it since in the Solr book I mentioned that 
"solr-php-client's use of JSON instead of PHP 
response writer highlights JSON usefulness for facilitating language agnostic 
communication between systems."!

Original comment by [email protected] on 4 Aug 2009 at 7:31