caching and naming other handles
Steve Huss-Lederman (firstname.lastname@example.org)
Fri, 6 Dec 1996 10:34:10 -0600 (CST)
I would like to raise new issue. At the last meeting we voted to
restrict naming to communicators and put the caching capability on new
handles (other than communicators) in the JOD. I view these two
decisions as related. Several people have expressed regret at these
decisions. I would be interested in gathering examples and reasons to
support putting the capability back on other handles and which handles
are really needed. I would also be interested in hearing from
implementors that these capabilities are or are not a problem. I
think we can make a push at the next meeting to reverse the decision
(if that is what comes out of the discussion), but we need to be armed
and ready this time.
P.S. - I also noticed I accidently completely removed the communicator
ID proposal. It will be put in JOD as voted at the last meeting.