Peter Firmstone wrote:
Dennis Reedy wrote:
On May 20, 2010, at 628PM, Peter Firmstone wrote:
We could call it api, instead of spec, so as not to confuse the Jini
Spec? (We call River an implementation of the Jini Specifications)
Implementation jar: service.jar
API jar: service-api.jar
Download jar: service-dl.jar
Thinking out loud here, what id the service does not use a smart
proxy? There is no difference between the API jar and the DL jar. Is
the API jar only needed when the service uses a smart proxy?
Yep that's correct.
I'm not sure I understand whether we want isolate just interfaces and and
referenced abstract types, or the impls as well, into the API jar. It sounds
like we are assuming that types referenced by the service interfaces don't need
authorization? I'm worried about that. There are serializable types in the JDK
that do work that might require authorization aren't there?
Gregg Wonderly
