Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 27 MAR 1998 11:49:26AM abjones wrote:

I would like to display a timed message on the console

of a web server running OICGI and INET_GATEWAY as a

debugging tool. It seems the INET_GATEWAY executable

does not provide a usable @WINDOW property for MSG.

Currently I am writing debugging messages into a file

that I can query from a web browser, but this is not

what I want for early development when I have access

to the server console and wish to follow the logical

path of a web process without having to hit "OK" at

every message. Any suggestions will be appreciated.


At 30 MAR 1998 12:54PM Gene Gleyzer wrote:

Abjones,

You are correct, INET requests are not setting @window to INET_GATEWAY. However, you can use INET_GATEWAY as the first parameter to MSG() anyway. In your situation I would recommend using "call send_info(infoString)" that will show infoString in the SystemMonitor window. You can disable system tracing messages by executing "run setdebugger 'spy', 0" from SystemMonitor.

Gene


At 31 MAR 1998 10:24AM abjones wrote:

This "old dog" has a lot of new tricks to learn. Thanks

for the tip on the SystemMonitor. I will try that for

my OI only routines relegating MSG to the thousands of

lines of "legacy" AREV code.


At 01 APR 1998 01:18PM Cameron Revelation wrote:

abjones,

Thanks for the tip on the SystemMonitor.

Also, if you want logging to show up in the INET gateway itself:

Send_Event(GS_MONITOR$, "OMNIEVENT", OUTCOMING$, Text)

Cameron Purdy

[email protected]

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/cef6a67718ecc734852565d40056ecad.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1