As I wrote earlier, the way Blunt is embedded into the communication framework on the Newton is not ideal. Some of the serive routines such as discovery or link handling is part of the connection procedure, which makes error handling quite sensitive. If something goes wrong, the serial port is busy and the Newton needs a restart.
Blunt 2 will work differently, it is an always-on Bluetooth stack. It will come with a new comm tool which will talk to this stack via events. The Bluetooth part would be working all the time, and any errors on that side will not be propagated to the NewtonScript or Endpoint side. The downside is that this take a bit to develop, but the huge advantage should be more reliable operations.
Posted by Eckhart at December 2, 2004 09:41 AM