Remarks on Micro Tango III
Some interesting events are associated with Jini enabled entities registering themselves in a lookup service which registration generates events
For a pager, use one with a digital interconnect. It is essentially permanently connected
For a Palm V, buy digital modems and assume they intermittently dial in to connect to Micro Tango Agent
- This sends summary of events that have received while palm disconnected. One can choose to discard or process
- email conduits could be useful resource
- One can from PC or Micro device, set flags to control which events are queued
Note that current Tango JavaScript shared browser (JSSB) has some similarities in architecture with that proposed here.
- JSSB has two major windows. One (called by Tango) queues all incoming Tango messages. These are looked at in a continuous 0.5 second cycle and either executed, deferred or discarded. This architecture is required as one must wait for browser to load pages before enacting page associated events
- AS with JSSB, this architecture naturally supporting event archiving.
Initial steps include thoughtful choice of hardware