Mike Caplan (in pecl bug #10994) has raised the question of whether,
when a business exception is raised in a component that has been
called remotely - through a web service, say - the exception should be
serialised and flowed back, then deserialised and rethrown in its
entirety on the calling end. At the moment the exception is recreated
in loving detail, with the same backtrace, line number, file name,
that it had on the remote end. This makes the exception identical
regardless of whether the components are local or remote. Mike
suggests that that is too much information and it would be better to
keep just the text and number. I can see his point. Perhaps it was a
step too far to flow back the backtrace. One possibility is to put the
behaviour under control of a config setting somewhere.

What do other people think?


You received this message because you are subscribed to the Google Groups 
"phpsoa" group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to