home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!zaphod.mps.ohio-state.edu!ub!galileo.cc.rochester.edu!rochester!cornell!taurus!rcbc
- From: rcbc@taurus.cs.cornell.edu (Robert Cooper)
- Newsgroups: alt.soft-sys.tooltalk
- Subject: Re: Tooltalk application questions...
- Message-ID: <RCBC.92Nov18124128@taurus.cs.cornell.edu>
- Date: 18 Nov 92 17:41:28 GMT
- References: <2b06eae7.6ae4@firefox.csc.calpoly.edu> <BUZZ.92Nov18095847@lion.bear.com>
- Sender: rcbc@cs.cornell.edu (Robert Cooper)
- Reply-To: rcbc@cs.cornell.edu
- Organization: Cornell Univ. CS Dept, Ithaca NY 14853
- Lines: 34
- In-Reply-To: buzz@bear.com's message of 18 Nov 92 14:58:47 GMT
-
- 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
- --
- --
-