Sequence Cooperative - DMS - February 2003 - by Bob Le Gob


Overview:
*********
The Sequence Cooperative module triggers a chain of actions.
The events triggering the chain of actions are triggered
on server side.


Editor:
*******
- Length: Enter the length of your sequence (number of 
          “output” events of the module instance).


Implementation:
***************
Actions:
- register         (S) : Registers client
- unregister       (S) : Unregisters client
- inputOneByOne    (S) : Each time this action is activated, 
                         it triggers a out'n' event, starting
                         from out1, then out2, then ..., then
                         out'length', then out1 again.
                         The event is sent to all registered
                         clients.
- inputAllAtOnce   (S) : When this action is activated, all
                         events from out1 to out'length' are
                         triggered one after the other.
                         The events are sent to all registered
                         clients.
                         This doesn't impact the inputOneByOne
                         action current status.
Events:
- registered       (S) : Client registered
- unregistered     (S) : Client unregistered
- out'n'           (S) : Output n triggered


Notes regarding Sequence 3.1 module:
************************************
- In Sequence module, all out'n' events are triggered on server side.
- As the module is only running on server side, this require 
constant client/server communications, be it useful or not.
- If you trigger the events all at once, linked client actions
will be run only on the client who triggered the events.
- If you trigger the events one by one and link them to client
actions, these actions will occur on the clients who triggered
the events. For example, if a client triggers out1, he will get
the action linked to out1, but if another client then triggers
out2, this other client will get the action linked to out2. The
first client doesn't get the second action, and the second client
doesn't get the first one.


Notes regarding Sequence Cooperative 1.0 module:
************************************************
- All out'n' events are triggered on server side.
- Client/server communications are constantly used but this is normal
regarding the purpose of the module.
- Triggering the events all at once now triggers the linked client 
actions by all registered clients.
- Triggering the events one by one now triggers the linked client 
actions by all registered clients.
- CAUTION: The cooperative side of this module has to be handled with 
care. It's bandwidth consumming and should not be used to trigger
other server actions (because of the numerous events triggered and
possibly triggered thereafter) except if needed and carefully thought.