<div class="node-signature"><div class="node-inheritance"><span class='node-name'>Route</span> : <span class='implementation-names'>XSeen</span> {</div>
<div class='node-fields'>
<div class="node-field"><div class="field-type">SFString</div><div class="field-access">[]</div><div class="field-name">source</div><div class="field-default"></div><div class="field-range">ID value</div></div>
<div class="node-field"><div class="field-type">SFString</div><div class="field-access">[]</div><div class="field-name">event</div><div class="field-default"></div><div class="field-range">Event name</div></div>
<div class="node-field"><div class="field-type">SFString</div><div class="field-access">[]</div><div class="field-name">destination</div><div class="field-default"></div><div class="field-range">ID value</div></div>
<div class="node-field"><div class="field-type">SFString</div><div class="field-access">[]</div><div class="field-name">field</div><div class="field-default"></div><div class="field-range">Field name</div></div>
</div><br>
}</div>

<p>The <strong>Route</strong> node establishes an event handlig mechanism between the identified source and evet type to the specified destination. All events handled with <strong>Route</strong> shall&nbsp;be DOM events, but they need not be DOM-defined events - custom events&nbsp;may be used. The event <em>source</em>&nbsp;is specified by the value of the <em>id</em> attribute. [Note: potentially expand to any unique node reference or even multiple node references. Multiple node references creates multiple event handlers.] The <em>event</em> name (or type) must also be specified (DOM requirement).&nbsp;</p>

<p>The <em>destination</em> node/tag is specified by the value of the <em>id</em> attribute (see note for <em>source</em>), along with the <em>field</em> in the node to receive the event.&nbsp;</p>

<h3><em>Future note</em></h3>

<ol>
<li><em>Allow the source to specify any unique node via class, ID, and node name.</em></li>
<li><em>Allow source to specify a collection of nodes. An event handler would be created for each one</em></li>
<li><em>Allow desination to specify any unique node </em></li>
<li><em>Allow destination to specify a collection of nodes. A listener would be established for each destination node.</em></li>
<li><em>Allow developer&nbsp;to specify a custom event handler (JavaScript code) that processes the event prior to passing it to the node's&nbsp;field's event handler.</em></li>
</ol>

<p>&nbsp;</p>