Event Driven Programs (Connect, Disconnect, Arrive, Depart, HeartBeat)

Correct way to troubleshoot such a program is to create an action as follows:

  1. @action Queued event.=me
  2. @link Queued event.=<my program to test>

The part "Queued event." is very precise. The case matters if you are going to imitate what the muck sets the command variable to exactly. The period must be included. Okay, then when you need to test the program you must include the event type on the stack as follows:

Event Type Test Command
Connect Event Queued event. Connect
Disconnect Event Queued event. Disconnect
Arrive Event Queued event. Arrive
Depart Event Queued event. Depart
Heartbeat pulse Event Queued event. HeartBeat

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <h3> <h4> <h5> <h6> <blockquote> <iframe>
  • Lines and paragraphs break automatically.
  • Use [fn]...[/fn] (or <fn>...</fn>) to insert automatically numbered footnotes.
  • Use [# ...] to insert automatically numbered footnotes. Textile variant.
  • Web page addresses and e-mail addresses turn into links automatically. (Better URL filter.)
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <c>, <cpp>, <drupal5>, <drupal6>, <glow>, <muf>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Images can be added to this post.

More information about formatting options