Max,
One question. Would this mechanism work for any possible GSS security
mechanism?
In other words, is all the information you need encapsulated inside a single
GSSCredential object?
Also, java.net.Authenticator was designed very much for the original
HTTP authentication
schemes (Basic and
Changeset: 7264cacbddaa
Author:alanb
Date: 2009-03-27 15:24 +
URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/7264cacbddaa
6693490: (se) select throws "File exists" IOException under load (lnx)
Reviewed-by: sherman
! src/share/classes/sun/nio/ch/SelChImpl.java
! src/solaris/cla
Changeset: 07da2ffbb76b
Author:jjg
Date: 2009-03-30 15:08 -0700
URL: http://hg.openjdk.java.net/jdk7/tl/langtools/rev/07da2ffbb76b
6819246: improve support for decoding instructions in classfile library
Reviewed-by: ksrini
! src/share/classes/com/sun/tools/classfile/Code_attribute.
On Mar 31, 2009, at 12:47 AM, Michael McMahon wrote:
Max,
One question. Would this mechanism work for any possible GSS
security mechanism?
In other words, is all the information you need encapsulated inside
a single
GSSCredential object?
Yes, this object is enough to perform a delegated
