sequencing in bracelet and controller

the SLInnerSequence object is truly central to this architecture. 
central, but under-developed.

- idea was to abstract out the order of assets to run for a given asset
- want to re-use them and recursively call them without needing to generate
another xml subset (sl supports limits characters via http)
- must support true sequencing, ie. timer() event waits for objects to
terminate b4 proceeding to next one: controller in the 'main' sequnce
dispatcher, each bracelet does it at the micro level over many users
- main script determines the user with longest Asset duration, waits for
that b4 proceeding to next asset
- for any parcel media, this will override OL text on screen. therefore, we
must still somehow 'give' the current node's text to the user: maybe chat
over public channel, or IM... or maybe automatically delay the changing of
parcel URL to at the very least flash the OL text on screen...
- any asset who's type has assettype.hasDuration=1 must wait for each other
(or at least have that be an option, on a per-asset basis)

Original issue reported on code.google.com by sanchore...@gmail.com on 19 Nov 2009 at 5:45

sivarajankumar / nosm-verse

sequencing in bracelet and controller #39