Marko,
1) Integrating madExcept in our applications was very simple. We use it in
all of our client and server applications. In addition, we use some of its
features to customize what exceptions should be logged based on their type.
We prefer not to log our custom exceptions that we raise to inform the user
of problems based on their use of the application. What we want madExcept
to do is handle those situations that we did not anticipate, or where
environmental problems cause an exception, or to report a possible bug to
us. In addtion, we create daily log files so that we can track any errors
based on usage and traffic patterns.
2) madExcept will catch all exceptions regardless of their source. You can
alter this behavior to handle some exceptions yourself and let madExcept
handle the rest. It is very flexible to implement as little or as much of
its behavior depending on your needs. You can work with it in code or in
the IDE which makes it a very easy tool to work with, without sacrificing
its flexibility and power.
3) Yes, as a matter of fact, it did. I inherited a very interesting
non-visual ISAPI (like a Web service) application that had been in
development for a while by another developer. He had left the project but
left a lot of general purpose library code along with the ISAPI application.
The ISAPI application would occassionally have strange access vialations
raised when traffic was heavy, but we could not track down the problem in
and reproduceable manner. Then I read a review of madExcept in Issue #89
(January 2003) by Dave Jewell. We got a copy of it and were able to track
down a very interesting garbage pointer problem that would occur in certain
instances on the Web server. It was a life saver. Since then, madExcept
has been integrated in all of our applications.
Finally, I had the pleasure of working with the developer of madExcept on
the ISAPI implementation. We wanted to use madExcept in our brower based
ISAPI applications to enable the user to have a robust exception handling
experience similar to that available with madExcept in a client Windows
application. Once we outlined what we wanted and wrote an example ISAPI
application for him to use during testing, he was able to exceed our
requirements. Now that functionality is a part of the shipping madExcept
product and we are very pleased with it and so are our users.
Mark
"Marco Sella" <
XXXX@XXXXX.COM>writes
Quote
Mark,
1. How easy was it to integrate MadExcept into your ISAPI application?
2. Does MadExcept catch *all* exceptions, or are there some that it
doesn't
or can not handle?
3. Did MadExcept help you catch exceptions in your ISAPI app that you
would
not have discovered otherwise?
Thanks.
