[Isolate-interest] second public review of the JSR 121

[Patrick Tullmann]

Great to see JSR-121 is still alive!

> FYI: work on this JSR has recently been resumed, and the result is posting
> a proposal for the second public review:
>
> http://jcp.org/en/jsr/detail?id=121

Nice!  This looks like a great API.  Its certainly smaller than some
previous iterations I've seen, but I can't think of much that is
actually missing...  :)  Fits nicely in a single package which is good.

There is an extraneous "{" in the first para of the 'Status Links'
section of the Link class doc.

Rename ClosedLinkException to LinkClosedException?  (I can imagine
this has been brought up before...)

'open' is an odd name for the LinkMessage getter.  Perhaps this is
some new Java convention of which I'm blissfully unaware ...  That
said, this is a nice interface for demultiplexing a LinkMessage's
contents.  Still, I'd call it 'get'...  ("open" is something you do
once and have to undo with a "close".)  Maybe 'contents' or
'getContents' if 'get' is too generic ...

Why no support for open files and open pipe ends in Messages?  The
open file ends would be nice for isolating secure code for opening and
accessing files from the isolated code that actually operates on the
open descriptor.  Especially since such streams are implicitly
passable via the StreamBindings.  (Maybe let me pass a StreamBindings
via a Link?)

Could you side-step some of this by adding a parameterized 'put'
method:
   public static <T> void newMessage(<T> type);
(Again, I'm totally ignorant of this new fangled parameterization
syntax, so perhaps this is obviously bunk.)

-Pat

----- ----- ---- ---  ---  --   -    -      -         -               -
Pat Tullmann                                     tullmann at flux.utah.edu
              The early bird gets the worm, so sleep in.