: > I don't see anything about it in RFC 4627 (which seems to be the most : > current JSON spec) so perhaps this is just a bug in the PHP json parser? : : : i try php with encode and decode. It works well although it has "@" : : so i don't think it is php's bug
I odn't know jack about PHP, when you talk about "encode" and "decode" in the context of this thread i'm taking your word for it that these are JSON related methods ... my point is that the JSON RFC doesn't say anything about needing to treat "@" charactesr as special in strings, so if you are seeing weird behavior parsing Solr's JSON response format using your "decode" PHP function when the data contains "@" symbols, the problem may be in the decode function ... just becuase it works properly with data from your "encode" function doesn't mean it's correct, it just means those two functions are consistent. i can write a pair of encode/decode functions that work together -- but that doesn't mean they work with legal JSON. Could you provide *any* more details about the problem you are having? - an example ofhte Solr response that causes the problem? - the error your get form your PHP call? - etc... -Hoss
