From kato-spec-return-90-apmail-incubator-kato-spec-archive=incubator.apache.org@incubator.apache.org Tue Apr 07 09:49:39 2009 Return-Path: Delivered-To: apmail-incubator-kato-spec-archive@minotaur.apache.org Received: (qmail 20307 invoked from network); 7 Apr 2009 09:49:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Apr 2009 09:49:38 -0000 Received: (qmail 70926 invoked by uid 500); 7 Apr 2009 09:49:38 -0000 Delivered-To: apmail-incubator-kato-spec-archive@incubator.apache.org Received: (qmail 70896 invoked by uid 500); 7 Apr 2009 09:49:38 -0000 Mailing-List: contact kato-spec-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kato-spec@incubator.apache.org Delivered-To: mailing list kato-spec@incubator.apache.org Received: (qmail 70886 invoked by uid 99); 7 Apr 2009 09:49:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 09:49:38 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.98.31] (HELO brmea-mail-1.sun.com) (192.18.98.31) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 09:49:28 +0000 Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n379n6dY015659 for ; Tue, 7 Apr 2009 09:49:06 GMT MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_LtZGuAzWA2CLUrs1oMGZrw)" Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KHQ008005UHUF00@mail-amer.sun.com> for kato-spec@incubator.apache.org; Tue, 07 Apr 2009 03:49:06 -0600 (MDT) Received: from [129.150.19.23] ([unknown] [129.150.19.23]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KHQ00HBG5XT8570@mail-amer.sun.com> for kato-spec@incubator.apache.org; Tue, 07 Apr 2009 03:49:06 -0600 (MDT) Date: Tue, 07 Apr 2009 04:48:57 -0500 From: Nicholas Sterling Subject: Re: Kato API javadoc In-reply-to: Sender: Nicholas.Sterling@Sun.COM To: kato-spec@incubator.apache.org Message-id: <49DB2189.3030602@Sun.COM> References: <49D9AF7A.5080802@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) X-Virus-Checked: Checked by ClamAV on apache.org --Boundary_(ID_LtZGuAzWA2CLUrs1oMGZrw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Thanks, Steve. Nicholas Steve Poole wrote: > On Mon, Apr 6, 2009 at 8:30 AM, Nicholas Sterling >> wrote: >> > > >> Steve, if we do end up having a concall, which I think would probably help, >> would you mind if I invited Alan Bateman of the HotSpot team to attend? >> > > > Sure that would be fine. > > >> Nicholas >> >> >> >> Steve Poole wrote: >> >> >>> Well at last ! - we actually have the API javdoc available - it's here >>> http://hudson.zones.apache.org/hudson/view/Kato/job/kato.api-head/javadoc/ >>> >>> I'm certainly not going to hold this up as a the greatest javadoc in the >>> world but its a good place to start. I do feel that we have finally >>> arrived :-) >>> >>> The API has lots of "DTFJ"ness to it that needs to go but I'm really >>> interested in intitial reactions to the javadoc - is the form of the API >>> what you expected? >>> >>> >>> Moving on - there is still code needed to make the API work (we need to >>> get >>> the hprof support working) but we can make progress in the interim. I >>> want to move quickly towards having a regular heat beat where we are >>> moving >>> through the usecases that we have. To do that we need to get up to >>> speed >>> with the API shape as it stands today. Stuart has published some info >>> on >>> the API but its not really sufficent for educational needs :-) >>> >>> Is it worth holding a conference call so that we can walk through the API >>> to >>> explain why its the shape it is or is everyone comfortable with just more >>> doc? >>> >>> Cheers >>> >>> Steve >>> >>> >>> >>> > > --Boundary_(ID_LtZGuAzWA2CLUrs1oMGZrw)--