Jim Hurley wrote:
> Besides the 'name question' -- are there any other questions or issues
> associated with the JiniProposal that we could be discussing?
Since resolution on the name question (so far) seems clear as mud :(
let's try a related question of Java package names. The existing
codebase (proposed as starting point for the project) uses these
package namespaces:
net.jini
com.sun.jini
com.artima.lookup
Can an ASF-approved project continue to use these?
The net.jini namespace is used for public APIs that are defined
by specifications that are currently Jini Community Standards.
These specifications are likely to come under the control of
the ASF project, rather than being governed by an outside body.
Lots of existing application code in the world makes calls on
these APIs, so having to change this namespace would be a
monumental upheaval, in my opinion.
The com.sun.jini and com.artima.lookup namespaces are mostly used
for implementations, although there are various APIs in the
com.sun.jini namespace that are used directly by applications.
Changing these namespaces would have less of an impact on
other Java source code out there, but the reality is that
lots of configuration files and startup scripts in the world
make reference to things in the com.sun.jini namespace, so
the impact would be felt there.
- Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
