Summary
Important Observations
- Signals are asynchronous. When you fire them and when they are received and actioned are not synchronous events. Sometimes they are synchronous, sometimes they are not. You should always code your applications as if they are asynchronous.
- You should develop a naming standard for your signal identifiers and document all signals used and their associated payloads.
- Signals are relatively expensive requests. They should action high level things like EMPLOYEE_UPDATED or LIST_DATA_CLEARED, rather than low level things like MOUSE_MOVED.
- A RAMP destination screen’s vHandle_AVEVENT function only listens for signals when it is the currently displayed 5250 screen (ie: only the current RAMP screen can listen for signals).
- The second parameter (Sender) passed to vHandle_AVEVENT functions is only available in WIN applications. In WEB and .NET applications this parameter is not available and is always passed as an empty string.
- Any RAMP destination screen may have its own unique vHandle_AVEVENT function.
What You Should Know
- How to signal events between filters and RAMP command handlers