Hi!
week or two and I serialize exceptions (excluding stack trace arguments)
to send them back to the calling process to aid in debugging process
failures.
But then you don't need to serialize Exception. You need to send the
text representation of Exception, for humans to look at, not the live
Exception object. Sending the actual object would be next to impossible
anyway (i.e. how you send over the live DB connection on DB query
exception?).
But the text representation includes the exception message, code, and
the stack trace. That's pretty much the whole thing. But you are right,
I don't want (and couldn't transfer) the live objects related to the
stack trace, if that's what you're referring to. That's why I would omit
the arguments in each stack trace item during serialization, because who
knows what it could be.
I just think that serializing exceptions is a buggy feature right now,
and we should fix the feature instead of throwing it out.
--
Stephen Coakley
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
