This is version 3.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
ScriptContext in SEA
ScriptContext describes a system for asynchronous drivers
in SICS/SEA written in Tcl. Such a driver is a collection
of configuration and action scripts.
The action scripts are called from the ScriptContext system
with in a certain context: a sics hipadaba node and a
controller object. The access to the context is implemented
with the sct command.
Initialization Script
The scripts should be placed in a
file with a path ~/sea/tcl/drivers/<driver-name>.tcl
If different drivers share common code, the common code may
be placed in ~/sea/tcl/common/. The individual drivers
may then contain only an appropriate source command.
The initialization script must have the name
stdConfig::<driver-name>.
The first command to be called is one of:
controller <protocol> <protocol parameters...>
controller std <send terminator> <timeout> <reply terminator> <separator>
controller bin <crc-algorithm> <timeout>
Other protocols than std and bin might be programmed in the core SICS code,
in fact there are already a couple of them programmed by Mark Koennecke.
For some needs, it might be easier to enhance the std or bin protocol.
return value is 1 when the controller was created, 0 when
it existed already (the return value may be needed if several
object share the same controller, and the initialization of
the controller properties have to be done only once).
This particular version was published on 10-Sep-2010 10:37:38 UTC by MarkusZolliker.
|