Hi Ken,
That's fine news.
Is any of that old, dead Java project eligible for release
as Open Source? What can you tell about what you have?
- mtw
Ken McDonell wrote on Mon, Apr 04, 2005 at 09:49:41AM +1000
We have an old (dead) Java project within SGI ... we never released this
and it is moribund.
If there is wider interest, I'd be receptive to any proposals as to how
we might be able to assist.
On Sun, 3 Apr 2005, Mike Werner wrote:
> Hi Steve,
>
> Regarding Java, I have just recently begun exploring the
> idea of a JNI implementation. You seem much further along.
>
> Are you planning to release it?
> Are you interested in collaborating?
> How complete is your wrapping of the PMAPI?
>
> - mtw
>
> Stephen Przepiora wrote on Fri, Apr 01, 2005 at 08:27:32PM -0500
>
> Have you tried JNI? I have the beginnings of a JNI implementation, but
> stopped because I needed to use it in a threaded enviroment. I am
currently
> reworking how the application will run.
>
> Steve
>
> On Apr 1, 2005 11:55 AM, Mike Werner <mtw@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Ken & Mark
> >
> > Thanks for the helpful info.
> >
> > Ken - as to why: I'm exploring some hairbrained ideas
> > for using pcp data without C, e.g. Java. Do you know
> > of any ports for alternate languages?
> >
> > - mtw
> >
> > kenmcd@xxxxxxxxxxxxxxxxx wrote on Fri, Apr 01, 2005 at 12:15:11PM
+1000
> >
> > On Thu, 31 Mar 2005, Mike Werner wrote:
> >
> > > PCP Team,
> > >
> > > Is there a specification (ASN.1 or otherwise) of the
> > > PMCD-to-client protocol, which I might obtain?
> >
> > I can assure you it is _not_ ASN.1 ... PCP is for analyzing
performance
> > problems, not creating them ... 8^)>
> >
> > The message protocol and format is not a secret
> >
> > pminfo -D pdu -v
> >
> > will dump out the messages flowing in both directions between the
> > client and pmcd.
> >
> > We don't have any documentation beyond that ... but more to the point
> > I'm kinda curious as to why you're interested in this, as the only
> > sensible way to use the infrastructure is via libpcp and there is
> > detailed documentation available on that API.
> >
> > Roughly, each libpcp call maps onto 1 sent message and 1 received
message.
> >
> >
>
|