In response to Terry Chay's response about his previous blog post, Frank Kleine has posted a few more comments on the topic of object serialization and some of the assertions Terry made.

Terry Chay made some remarks to my last blog entry about a solution for lazy class loading without using __autoload(). Some of his statements seem like I explained my implementation not good enough leading to wrong interpretations. In this blog entry I'll use some of his statements to take a deeper look into my implementation and show that he has drawed some conclusions which I want to disprove.

He goes back and corrects some of what Terry has said in his response, including showing a more detailed version of him implementation. Be sure to check out the comments for the post, though - Terry comes back and clarifies some of the comments he'd made including the framework talk and changes of perspective having seen the new code snippet/information.

In response to Terry Chay's response about his previous blog post, Frank Kleine has posted a few more comments on the topic of object serialization and some of the assertions Terry made.

Terry Chay made some remarks to my last blog entry about a solution for lazy class loading without using __autoload(). Some of his statements seem like I explained my implementation not good enough leading to wrong interpretations. In this blog entry I'll use some of his statements to take a deeper look into my implementation and show that he has drawed some conclusions which I want to disprove.

He goes back and corrects some of what Terry has said in his response, including showing a more detailed version of him implementation. Be sure to check out the comments for the post, though - Terry comes back and clarifies some of the comments he'd made including the framework talk and changes of perspective having seen the new code snippet/information.

In response to a post from the Stubbles blog, Terry Chay has posted some of his thoughts about the serialization solution presented in the other post.

Frank Kleine writes a PHP 5 framework called Stubbles. I have a long-standing view about frameworks that hasn't changed one bit. But instead of arguing about the Sysaphean task Frank is engaging in, I'll show what my approach is to one small component (while being a bit jealous that he can actually develop in PHP 5).

Frank's solution involves storing the objects in the session, serializing them first. The issue comes up when the class(es) the object needs aren't included into the page. Terry offers a different sort of solution - one also using __autoload, but using it combined with unserialize_callback_func.

Terry compares this with Frank's approach and notes that his method "closes off" the system from the very PHP functions that could make his life simpler (making a separate handling system). He also includes a method for doing the same when all you know is the class file's name (non-PEAR format).

In response to a post from the Stubbles blog, Terry Chay has posted some of his thoughts about the serialization solution presented in the other post.

Frank Kleine writes a PHP 5 framework called Stubbles. I have a long-standing view about frameworks that hasn't changed one bit. But instead of arguing about the Sysaphean task Frank is engaging in, I'll show what my approach is to one small component (while being a bit jealous that he can actually develop in PHP 5).

Frank's solution involves storing the objects in the session, serializing them first. The issue comes up when the class(es) the object needs aren't included into the page. Terry offers a different sort of solution - one also using __autoload, but using it combined with unserialize_callback_func.

Terry compares this with Frank's approach and notes that his method "closes off" the system from the very PHP functions that could make his life simpler (making a separate handling system). He also includes a method for doing the same when all you know is the class file's name (non-PEAR format).