I would like to talk about pervasive devices and applications. There are a variety of devices, each designed to satisfy different needs and reflecting different trade-offs, such as ease of use, ease of wear, functionality, speed and connectivity. People use a number of devices based on these design points and trade-offs. These devices, including a PC, Notebook, Tablet-PC, PDA, cell phone, and in some cases even a watch, can run applications. This leads to the possibility of having important applications, like your calendar, available no matter what device you happen to be carrying or using at the time. Another interesting scenario involves a group people using copies of a common application and needing to see common view of the data. The problem is how to keep the data in sync between this disparate application instances.
A solution to this problem is proposed by a new ETTK technology called Fluid Sync. It provides a model in which data flows between applications like a "fluid." If all devices are connected, data changes are sent directly to the devices. If a device is not connected, it can get the update the next time it connects. Likewise if a person makes updates while disconnected, the updates will be distributed later, once the device connects.
Fluid Sync provides code that runs on a small server and on each of the devices. It is a light-weight application enablement middleware that provides very sophisticated support using open standards wherever available. Fluid Sync will allow us to explore new models of application usage and team collaboration. I'll give more information in future postings.