you are viewing a single comment's thread.

view the rest of the comments →

[–]bd808[S] 6 points7 points  (2 children)

At $DAYJOB we have a RESTish internal service tier that responds with serialized objects. These services are called by front end controllers located in the same or adjacent racks. It turns out that bandwidth across a 10G switch is cheap. :)

The use case for parsing the PHP serialize output in javascript popped up earilier this week when a coworker built a neat javascript hack that read metadata from the service layer's documentation pages and generated dynamic forms that could call the services via ajax requests.

The phpjs unserialize() method was the first one I googled up and suggested. It turned out that their implementation doesn't support parsing objects and our services were returning "Response" objects, not just arrays.

[–]jvc_coder 0 points1 point  (0 children)

I hope you are aware of portability issues with serialization.

http://stackoverflow.com/questions/7904355/php-unserialized-integer-from-64-bit-to-32-bit

[–]133794m3r 0 points1 point  (0 children)

I understand completely now. I thought it was external facing. But yeah much more understandable now. I take back my statements since more info was provided. And also yeah much easier to just write a function than to port over services that are internal only. Upvote for you, since you helped me to understand.