You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kato-commits@incubator.apache.org by mo...@apache.org on 2009/08/10 13:21:33 UTC
svn commit: r802784 -
/incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml
Author: monteith
Date: Mon Aug 10 13:21:32 2009
New Revision: 802784
URL: http://svn.apache.org/viewvc?rev=802784&view=rev
Log:
Add more detail to todo.xml explaining what is missing.
Modified:
incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml
Modified: incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml
URL: http://svn.apache.org/viewvc/incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml?rev=802784&r1=802783&r2=802784&view=diff
==============================================================================
--- incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml (original)
+++ incubator/kato/trunk/org.apache.kato/kato.docs/src/docbkx/chapters/todo.xml Mon Aug 10 13:21:32 2009
@@ -29,36 +29,65 @@
<sect3>
<title>Native and Java Frame interleaving</title>
+ <para>
+ The API presents native stack frames and Java stack frames in different places in the API - in ImageThread
+ and JavaThread. This makes it difficult to understand the order in which Java methods and native functions
+ have been called. Exposing the interleaving of native and Java frames would help, for example, debugging
+ complex JNI functions.
+ </para>
</sect3>
<sect3>
- <title>Optimization of data access (query support)</title>
+ <title>Optimisation of data access (query support)</title>
+ <para>
+ The current programmatic means of accessing data is not open to optimisation. Having a query language
+ would enable the creation of useful indexes to speed up queries.
+ </para>
</sect3>
<sect3>
- <title>No support for identifing or handing generics in the Java Runtime</title>
+ <title>No support for identifying or handing generics in the Java Runtime</title>
+ <para>
+ Currently it is impossible to determine any of the generic type information that is available in
+ JVMs implementing Java 5.0 or above.
+ </para>
</sect3>
<sect3>
- <title>No support for thread groups in the Java Runtime</title>
+ <title>No support for thread groups in the Java Runtime</title>
+ <para>
+ The API has no consistent means of reporting the ThreadGroups the JavaThreads belong to.
+ </para>
</sect3>
<sect3>
- <title>Lack of consitancy in accessing JavaObjects</title>
+ <title>Lack of consistency in accessing JavaObjects</title>
<para>
- Accessing data as their own type is difficult or impossible.
+ In order to access the contents of objects in most cases it is often necessary to implement, as accesses
+ via the API, at least a subset of the functionality of the methods in the class of the object being accessed.
+ For example, to access all of the objects in a java.util.HashMap, knowledge of how HashMap is
+ implemented is necessary. As HashMap can be implemented differently on different implementations of the
+ Java SDK, it is difficult to write programs using the API that are truly Java SDK agnostic.
</para>
</sect3>
<sect3>
<title>Need defined behaviour on what toString offers on each part of the API</title>
+ <para>
+ The toString() method's behaviour is not specified in sufficient details across the whole API.
+ For example, JavaStackFrame.toString() should return a string describing the stack location
+ like in a Java stacktrace, so this should be specified so it can be implemented consistently.
+ </para>
</sect3>
<sect3>
- <title>Can't see the finaliser info</title>
- </sect3>
-
- <sect3>
- <title>No definitions about snapshotting</title>
+ <title>No definitions about snapshoting</title>
+ <para>
+ It is desirable that there be a consistent means for generating dumps for later analysis
+ by the API. An API to be used during runtime would enable applications to generate dumps when
+ it suits them. This would not be to the exclusion of other means of generating dumps
+ peculiar to particular JVM implementations.
+ </para>
</sect3>
- </chapter>
\ No newline at end of file
+ </chapter>
+
\ No newline at end of file