NetTalk Central

Author Topic: Handling Error Messages  (Read 18643 times)

John Hickey

  • Administrator
  • Newbie
  • *****
  • Posts: 47
    • View Profile
    • Email
Handling Error Messages
« on: June 17, 2007, 03:11:53 PM »
On the Newsgroup, Rudi Havenga asked:

Is there a way to set the web server to not pop up with error messages on
the server itself. When a duplicate key is generated or a restricted
relationship is deleted, the server pops up with a message and the user's
system just hangs. What can I do about it?


Bruce Johnson answered:

the message box has to be suppressed using either
CapeSoft MessageBox (that's the easy way) or
by making your own message window (using system{prop:messagehook} )


Rudi then replied:

I made use of  system{prop:messagehook}

I have created a global queue that I populate with all the error messages.
My web server window I put my web server information on one tab and my error
messages on another.

Perfect.

And Roberto Artigas then chimed in:

Greetings Rudi - Nice queue idea.

I have hooked the messages (message, halt, stop) to make sure the web server
does not get hung with a console message coming from ABC or some other
place, this way I could log them or do something with them, I just had not
gotten around to a good way of dealing with them. I like your queue window
idea.

Thank you for sharing.


Finally, Sean Cameron (CapeSoft) said:

I'd probably use an IMDD table, as it's thread safe. I use xFiles to save queues and IMDD tables to disk as XML, which is also really fast.