Changeset: 8db45b13526e
Author:jjg
Date: 2012-10-15 17:07 -0700
URL: http://hg.openjdk.java.net/jdk8/tl/langtools/rev/8db45b13526e
8000666: javadoc should write directly to Writer instead of composing strings
Reviewed-by: bpatel
!
src/share/classes/com/sun/tools/doclets/formats/ht
Changeset: c0736b62160e
Author:robm
Date: 2012-10-15 22:34 +0100
URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/c0736b62160e
8000487: Java JNDI connection library on ldap conn is not honoring configured
timeout
Reviewed-by: vinnie
! src/share/classes/com/sun/jndi/ldap/Connection.
Alan,
Looks ok for me.
-Dmitry
On 2012-10-15 20:14, Alan Bateman wrote:
>
> java.net.URL guarantees that 5 protocol handlers are present: http,
> https, ftp, file and jar.
>
> ftp a legacy protocol and I'm wondering whether it's time to consider
> removing it from the list. I'm not suggesting
Yes, this seems reasonable to me too. There seem to be fewer and fewer
applications that use ftp...
- Original Message -
From: chris.hega...@oracle.com
To: alan.bate...@oracle.com
Cc: net-dev@openjdk.java.net
Sent: Monday, October 15, 2012 2:48:05 PM GMT -05:00 US/Canada Eastern
Subject: R
Seems reasonable.
-Chris
On 15 Oct 2012, at 17:14, Alan Bateman wrote:
>
> java.net.URL guarantees that 5 protocol handlers are present: http, https,
> ftp, file and jar.
>
> ftp a legacy protocol and I'm wondering whether it's time to consider
> removing it from the list. I'm not suggesti
On 15/10/2012 18:20, Mike Duigou wrote:
We should also nuke gopher and netdoc (in sun.net.www.protocol package)
I am not sure if mailto should continue as there are better solutions.
Mike
I agree there isn't any reason to continue to include gopher or netdoc.
I also agree with Guy's suggestio
We should also nuke gopher and netdoc (in sun.net.www.protocol package)
I am not sure if mailto should continue as there are better solutions.
Mike
On Oct 15 2012, at 09:14 , Alan Bateman wrote:
>
> java.net.URL guarantees that 5 protocol handlers are present: http, https,
> ftp, file and ja
What about including sftp?
On Monday, October 15, 2012, Alan Bateman wrote:
>
> java.net.URL guarantees that 5 protocol handlers are present: http, https,
> ftp, file and jar.
>
> ftp a legacy protocol and I'm wondering whether it's time to consider
> removing it from the list. I'm not suggesting
java.net.URL guarantees that 5 protocol handlers are present: http,
https, ftp, file and jar.
ftp a legacy protocol and I'm wondering whether it's time to consider
removing it from the list. I'm not suggesting we don't continue to
include it, rather just removing the guarantee that it is alw
