[OpenAFS-devel] Java JNI access to Venus, Vlserver and Volserver ??

Thu, 13 Dec 2001 01:26:59 -0800

--0__=07BBE1B3DF94D9668f9e8a93df938690918c07BBE1B3DF94D966
Content-type: text/plain; charset=US-ASCII

We have been using the admin libraries built out of the src/admin directory
to develop an administrative JNI.

The libraries supported through the JNI include the following libraries.
It appears that LWP is not used in these libraries and they should be
pthread safe.

libafsadminutil.a
libbosadmin.a
libcfgadmin.a
libclientadmin.a
libkasadmin.a
libptsadmin.a
libvosadmin.a

We are working on a Java programming interface spec for review/discussion
and hopefully standardization.   Let me know if you are interested and I
will keep you posted on our progress.

Shyh-Wei

Jim Doyle <doyle@theworld.com>@openafs.org on 12/04/2001 08:51:38 PM

Sent by:    openafs-devel-admin@openafs.org

To:    openafs-devel@openafs.org
cc:
Subject:    [OpenAFS-devel] Java JNI access to Venus, Vlserver and
       Volserver ??

Has anyone done anything w.r.t. writing Java JNI accessors to
native AFS APIs ?

Is it even possible to do this, given the fact that LWPs and
Java Threads (pthreads) in the same address space may conflict ?

It seems that a whole world of novel things could be done once
one had Java objects to cover these APIs. Further, the code base
could likely be shared with whatever exists of the DFS community and
what continues to exist with the Coda community -- at least with Venus,
since all three share the same style of interface.

I grow weary of writing Shell and Perl crud to automate AFS trivia..

-- Jim

_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel

--0__=07BBE1B3DF94D9668f9e8a93df938690918c07BBE1B3DF94D966
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body> 
 
We have been using the admin libraries built out of the src/admin directory to develop an administrative JNI. 
 
The libraries supported through the JNI include the following libraries. It appears that LWP is not used in these libraries and they should be pthread safe. 
 
libafsadminutil.a 
libbosadmin.a 
libcfgadmin.a 
libclientadmin.a 
libkasadmin.a 
libptsadmin.a 
libvosadmin.a 
 
We are working on a Java programming interface spec for review/discussion and hopefully standardization. Let me know if you are interested and I will keep you posted on our progress. 
 
Shyh-Wei

<p><font size="2" color="#800080">Sent by:	openafs-devel-admin@openafs.org</font>
<p><font size="2" color="#800080">To:	</font><font size="2">openafs-devel@openafs.org</font><br>
<font size="2" color="#800080">cc:	 </font><br>
<font size="2" color="#800080">Subject:	</font><font size="2">[OpenAFS-devel] Java JNI access to Venus, Vlserver and Volserver ??</font><br>
<br>
<br>
<br>
<br>
<tt>Has anyone done anything w.r.t. writing Java JNI accessors to<br>
native AFS APIs ?<br>
</tt><br>
<tt>Is it even possible to do this, given the fact that LWPs and<br>
Java Threads (pthreads) in the same address space may conflict ?<br>
</tt><br>
<tt>It seems that a whole world of novel things could be done once<br>
one had Java objects to cover these APIs. Further, the code base<br>
could likely be shared with whatever exists of the DFS community and<br>
what continues to exist with the Coda community -- at least with Venus,<br>
since all three share the same style of interface.<br>
</tt><br>
<tt>I grow weary of writing Shell and Perl crud to automate AFS trivia..<br>
</tt><br>
<tt>-- Jim<br>
</tt><br>
<tt>_______________________________________________<br>
OpenAFS-devel mailing list<br>
OpenAFS-devel@openafs.org<br>
</tt><tt><a href="https://lists.openafs.org/mailman/listinfo/openafs-devel">https://lists.openafs.org/mailman/listinfo/openafs-devel</a></tt><br>
<br>
</body></html>
--0__=07BBE1B3DF94D9668f9e8a93df938690918c07BBE1B3DF94D966--