Preliminary review: Adding tracing of I/O calls
jvanalte at redhat.com
Thu Nov 8 17:37:39 UTC 2012
----- Original Message -----
> From: "Staffan Larsen" <staffan.larsen at oracle.com>
> To: "mark reinhold" <mark.reinhold at oracle.com>
> Cc: core-libs-dev at openjdk.java.net
> Sent: Thursday, November 8, 2012 3:44:48 AM
> Subject: Re: Preliminary review: Adding tracing of I/O calls
> On 7 nov 2012, at 23:22, mark.reinhold at oracle.com wrote:
> > 2012/11/2 11:36 -0700, staffan.larsen at oracle.com:
> >> Webrev: http://cr.openjdk.java.net/~sla/iotrace/webrev.00/
> > Who (or what) is the intended consumer of the sun.misc.IoTrace and
> > IoTraceListener APIs? In other words, are these meant to be stable
> > external interfaces that we're going to support for use by
> > arbitrary
> > code over the long term?
> The primary intended consumer is Java Flight Recorder which is JDK
> > The reason I ask is that sun.misc is likely to go away in JDK 9, as
> > part of the modularization work. If these APIs are meant to be
> > used
> > by any code outside of the JDK then we should probably put them in
> > a more appropriate package now in order to avoid pain later on.
> I don't have any preferences. Can you suggest a better package?
I don't have a particular suggestion, but would like to just chime in
and say that there is interest in API such as this being public and
stable and available for use in tools targeting OpenJDK at some point.
(My understanding is that Java Flight Recorder is not part of OpenJDK)
More information about the core-libs-dev