I think I know the answer to this but think I'll ask anyway.
When my server starts up in installs an error handler, ON ERR
CALL("err_log_only"). As the name implies it simply logs errors and keeps
churning.
It doesn't seem to be called when a method called by Execute on server is
running. At least I'm occasionally seeing errors on the server from a
couple of methods. The thing about this is the process calling these
methods has its own error handler installed as well which is not being
called.
So, is this a bug or is it the case that methods running as EOS have to
explicitly call their own error handler? And if that's the case, as I think
about it, is this a situation like the rest of process vars and the 'twin'
process where it's the same but different. Ie, I can have process vars with
the same names on both the client and server side but these vars can have
totally different contents. Is it therefore the case with the Error
handler? Installing a given handler on the client process doesn't affect
the server side. If that's the case it sounds like I should be adding an
EOS method to my process init to install a handler on the server twin.
Anyone else encountered this? What did you do?
--
Kirk Brooks
San Francisco, CA
=======================
*The only thing necessary for the triumph of evil is for good men to do
nothing.*
*- Edmund Burke*
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
