7191556: (fs) UnixNativeDispatcher.getextmntent should be moved into platform specific code

Alan Bateman Alan.Bateman at oracle.com
Sun Aug 26 03:26:53 PDT 2012


On 23/08/2012 15:35, Andrew Hughes wrote:
> :
> True.  This actually sounds very much like cleanup work that could be a
> good introduction for new OpenJDK developers.  There's not any real
> code that's got to be written.  It just needs someone to find the
> Solaris/Linux/etc.-specific code, break it out into new files and
> test the result heavily.  At least, that's the impression I get.
Implementation-wise then some of it would be clean-up and refactoring 
but it's a direction that would require broader discussion and agreement 
first. The topic has been touched on various lists and not always clear 
to me that there is stomach for it (everyone is busy, it would be 
disruptive, etc.).  Once we get over the transition to the new build 
system then it may be a good topic to bring up again. AIX or other ports 
wanting to come into the main line is probably going to force a 
discussion too.

> :
> Sure, I can write something up.  I'm pretty much in the dark as the best
> package name to choose though (I wasn't aware of the significance of sun.misc
> either way).  I'm looking for something that would be usable by code in
> the NIO, net and AWT packages.  Any ideas?
I'm not sure about the package either but I don't think it matters too 
much at this point as long as it's not sun.awt (from a modularity 
perspective it is okay to have AWT -> core dependencies but core -> AWT 
is problematic). A possible starting point might be sun.util.gio or 
sun.util.gnomeservices and we figure the package name out later. It 
really depends on whether you are thinking about internal APIs for each 
of these or whether you are thinking of a facade.

-Alan.



More information about the nio-dev mailing list