Wow. Thank you so much! I need to read this all more thoroughly. I really
appreciate the suggestions and the help getting this on the correct mailing
list.
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E
://tools.ietf.org/html/rfc5246) in the TLS
negotiation, but since browser's don't enforce care, people are left thinking
everything is great (until Java tries to connect).
Thanks,
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, I
.
So, as for the bug report, I would hope that authentication be incorporated, or
at least considered, as part of a total solution.
I have seen some net-dev emails about authentication recently, so I am hoping
this can all be addressed in coordination.
Mark Claassen
Senior Software Engineer
I realize that no one probably knows who I am, however I have been using Java
since the 1.x days. I have probably spoken to several of you at previous
JavaOne’s. I am also a member of the CAP program.
Anyway, I would like to say that I like the idea of the incubator modules.
These things
000
schrieb "Mark A. Claassen" <mclaas...@ocie.net>:
> After asking some questions at JavaOne, I was told I could get more
> complete answers here. My question is about authentication mechanisms
> and support for native network configurations.
>
> Is t
After asking some questions at JavaOne, I was told I could get more complete
answers here. My question is about authentication mechanisms and support for
native network configurations.
Is the new client going to have access to the system proxy configuration
settings? It would be nice if
