🚀 go-pugleaf

In article <BUZZ.92Nov18095847@lion.bear.com> buzz@bear.com (Buzz Moschetti) writes:

   Things I don't like:
   1.  "Session" and "Local File" scopes work well, but "Network" scoped
       messages require a common NFS mounted file as a transport vehicle.  Oof.
   
   ...

   Things they should add:

   ...

   2.  Guaranteed serializable messages.  The messaging engine will
       automatically assign a sequential serial number to outbound messages
       and receivers will fault if a gap is detected.  The serial number of
       the first message received after registration becomes the initial
       comparison serial number; alternately, you can override with your
       own initialization number.  *Very* useful.


How much to people use the "network" scope? Is NFS reliability, "stale file
handle" and other effects a problem? Do other people think that sequential
ordering on messages is important?

I'm just trying to confirm my suspicion that Tooltalk has an easy-to-use and
flexible communication model, but that its distributed abilities could be
better. 

Also, would anyone like to compare Tooltalk with HPs Broadcast Message
Service?

              -- Robert Cooper
--
--