Directed messages sent to high level portals: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
2. Message handling to be encapsulated in a hidden portal (must be called<br /> _!message) rather than having to have message entries/flows right<br /> at the top portal, which may be visible to end users.<br /> | 2. Message handling to be encapsulated in a hidden portal (must be called<br /> _!message) rather than having to have message entries/flows right<br /> at the top portal, which may be visible to end users.<br /> | ||
---- | ---- | ||
[[Category:Object/Dispatcher]] | [[Category:Object/Dispatcher]] | ||
[[Category:Object/Entry]] | [[Category:Object/Entry]] | ||
[[Category:Object/Portal]] | [[Category:Object/Portal]] | ||
<font size="2">idkbase note 139</font> | <font size="2">idkbase note 139</font> | ||
Latest revision as of 22:03, 10 January 2008
A dispatcher or Routine line sending a message to a portal will now first attempt to match a message entry with the same name as the sending dispatcher/change object. If this fails, then the default entry (_!message)
is looked for. If this also fails, then the platform looks for a Portal called _!message and forwards the message to it.
Within this portal, specific entries may extract the message.
This enables
1. Many message types to be directed at a portal and then
individually handled within via separate entries.
2. Message handling to be encapsulated in a hidden portal (must be called
_!message) rather than having to have message entries/flows right
at the top portal, which may be visible to end users.
idkbase note 139