I don't understand.  I did the breakout of x-net...

Mikhail Loenko wrote:
Geir

Sounds like no one objects to the proposal itself, the discussion is about the
naming. Could you please approve/decline new componentization?

Thanks,
Mikhail

On 1/27/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:

Stepan Mishura wrote:
Sounds dirty.  How about security-x?

Ok. I named it by analogy with x-net. Your variant works for me.
x-net has the same issue for me.  I figure that net-x is better too
because it will sit next to net in a directory/IDE package tree, etc...
(just like security-x near security)

geir

Thanks,
Stepan


On 1/27/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
Sounds dirty.  How about security-x?

Stepan Mishura wrote:
I agree with the proposal and I'm ready to start working on a patch for
splitting 'security2' into suggested components and integrating them
with
the current build.

Also I'd like to suggest a name for a new component: 'x-security'.

Thanks,
Stepan Mishura
Intel Middleware Products Division



On 1/19/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
Hello

Let's start a different thread for that.

I suggest revisiting current componentization for security related
parts.
Now we have for example crypto architecture in security module but
crypto extension in the crypto module.

See natural components in the UserGuide
http://java.sun.com/j2se/1.5.0/docs/guide/security/

The proposal is to have 3 components:
1. general security & crypto
2. ssl
3. jaas

The logical content of those components would be:
1.
- General Security
- Certification Path
- JCE

2.
- JSSE

3.
- JAAS
- JGSS
- SASL


Physical content of those components:

1.
java.security
javax.crypto
javax.security.cert
2.
javax.net
3.
javax.security w/o javax.security.cert
org.ietf

Opinions?

Thanks,
Mikhail Loenko
Intel Middleware Products Division


--



--
Thanks,
Stepan Mishura
Intel Middleware Products Division



Reply via email to