Why php5 DomDocuments need to be un/serialize()able
posted: March 2nd, 2005 · by: Sven
In our last post about “Template playing with php5’s Dom” we shared some thoughts about how to build a basic templating engine based on php5’s build-in dom extension. I have been playing around with that and have to say I found php5 dom’s lack of being un/serialize()able really annoying.
Why would anyone want to php un/serialize() a php Dom tree? A dom can be “serialized” to Xml, that’s human readable and non-proprietary! Creating a DomDocument and getting some Xml parsed is fast.
So, what the *%#~ is this about?
Ok, let’s take a minute to investigate that. Here’s an answer.
Read the rest of this entry