index.html #1 

<HTML>

<HEAD>

<TITLE>
Perforce API Project
</TITLE>

</HEAD>

<BODY BGCOLOR="#FFFFFF">
<CENTER>
<P>
<A NAME="toc"></A>
<h2>
<sub><a href="../../index.html">Perforce Public Depot</a></sub><br>
The Perforce API Project
</H2>
<P>

<TABLE BORDER=0><TR><TD>
<B>
<UL>
<LI><A HREF="#about">About This Project
</A>
<LI><A HREF="#api">API Interfaces
</A>
<LI><A HREF="#toolkits">Interface Toolkits
</A>
</UL>
</B>
</TABLE>
</CENTER>
<br>
<br>
<br>

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="about"></A>
<H2>About This Project
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<p>
<table cellpadding=5%>
<tr>
<td valign=top>
<b>Content</b>
</td>
<td valign=top>
The "Perforce API Project" collects user-contributed interfaces
to allow programmatic access to Perforce. Most of these do so
by providing a layer between the the
<a href=http://www.perforce.com/perforce/doc.021/user/p4api.txt>
Perforce API</a> and a particular language; some use the Perforce
command line client.

<p>
(Also, see
<a href=../webkeeper/index.html>WebKeeper</a> for another Perforce
API implementation example.)
</td>
</tr>
<tr>
<td valign=top>
<b>Contributing</b>
</td>
<td valign=top>
Please contact <a href=mailto:opensource@perforce.com>Perforce</a>
if you have any submitted contributions you'd like integrated
into the public branch of the Perforce API Project.
</td>
</tr>
</table>

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="api"></A>
<H2>API Interfaces
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<DL>

<DT><B>
<A HREF="http://public.perforce.com:8080/@ra=s@/public/perforce/api/python/P4Client/">
//public/perforce/api/python/P4Client/
</A></b>
<DD>
P4Client, a Python interface to the Perforce ClientApi
class.
A Python review daemon script that uses it is provided as an example.
Contributed by 
<a href="http://public.perforce.com:8080/@md=d&ra=s@//mike_meyer?ac=17">
Mike Meyer</a>.

<P><DT><B>
<A HREF="http://public.perforce.com/guest/tony_smith/perforce/API/Perl/index.html">
//guest/tony_smith/perforce/API/Perl/
</A></b>
<DD>
A Perl interface to the Perforce API.
Contributed by 
<a href="http://public.perforce.com:8080/@md=d&ra=s@//tony_smith?ac=17">
Tony Smith</a>.

<P><DT><B>
<A HREF="http://public.perforce.com/guest/tony_smith/perforce/API/Ruby/index.html">
//guest/tony_smith/perforce/API/Ruby/
</A></b>
<DD>
A Ruby interface to the Perforce API.
Contributed by 
<a href="http://public.perforce.com:8080/@md=d&ra=s@//tony_smith?ac=17">
Tony Smith</a>.

<!--
  <P><DT><B>
  <A HREF="http://public.perforce.com:8080/@md=d&cd=//guest/michael_bishop/&ra=s&c=XEd@//guest/michael_bishop/P4APIForJava/?ac=83">
  //guest/michael_bishop/P4APIForJava/
  </A></b>
  <DD>
  A Java interface to the Perforce API.
  Contributed by 
  <a href="http://public.perforce.com:8080/@md=d&ra=s@//michael_bishop?ac=17">
  Michael Bishop</a>.
-->

</DL>

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="toolkits"></A>
<H2>Interface Toolkits
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<P>

These tools provide higher level capabilities (as opposed to the basic
API/language bindings in the <a href=#api>API Interfaces</a> section
above).

<DL>

<DT><B>
<A HREF="http://public.perforce.com:/public/perforce/api/java/p4package/index.html">
//public/perforce/api/java/p4package/
</A></b>
<DD>
P4Package, a high-level Java API for Perforce. These classes provide a
way to encapsulate source control objects like branches, files, users, etc.
This implementation is based on the execution of the Perforce command line
client, rather than the Perforce API proper.
Contributed by 
<a href="http://public.perforce.com:8080/@md=d&ra=s@//david_markley?ac=17">
David Markley</a>.

<P><DT><B>
<A HREF="http://public.perforce.com:/public/perforce/api/java/p4jsp/index.html">
//public/perforce/api/java/p4jsp/
</A></b>
<DD>

This application allows multiple users to access the perforce using
the same web application using their own credentials. This makes it
easy to add pages that implement other perforce functions and have
them execute using appropriate authorization. An example would be a
page that handled integrations from one branch to another at the click
of one button or link.

Contributed by 
<a href="http://public.perforce.com:8080/@md=d&ra=s@//david_markley?ac=17">
David Markley</a>.


</DL>

<br><br><br>
<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%>
<TR>

<TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=LEFT VALIGN=CENTER>
<FONT SIZE="-2">
Copyright &copy;<br>
1998, 1999, 2002<br>
<a href="http://www.perforce.com">Perforce Software</a><br>
</FONT>
</TD>

<TD WIDTH=70% BGCOLOR=FFCC66 ALIGN=CENTER>
<FONT SIZE="-2">
You're browsing a file stored as<br> 
<code>$Id: //guest/hari_krishna_dara/perforce/api/index.html#1 $</code><br> 
in the 
<A HREF=http://public.perforce.com/public/index.html>Perforce Public Depot</A>.
</FONT>
</TD>

<TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=RIGHT>
<FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</FONT>
</TD>

</TR>
</TABLE>
<!------------------------------------------------------------------>



</BODY>
# Change User Description Committed
#1 5093 Hari Krishna Dara Populating perforce branch.
I will be adding p4admin files to it.
//public/perforce/api/index.html
#12 1984 rmg Break the listing up into "API Interfaces" (for low level
API/language bindings) and "Interface Toolkits" (for
higher-level stuff)

Add p4jsp to the latter category.
#11 1701 rmg Don't advertise Michael's Java API for now, pending some docs.
#10 1698 rmg Add links to the Perl, Ruby, and Java (true p4api) interfaces.

For the moment, these go to //guest/tony_smith/... and
//guest/michael_bishop/..., which is a departure, but I don't
see any harm in it, nor any great advantage or urgency to
integrating them into //public.
#9 1697 rmg Note that some implementations may not use p4api
#8 1155 rmg The change to utils/index.html was required to get the page
       to render better with Netscape 6.2. (Without the closing </B>
       tags, the whole page from the Depot Browsers section on down
       rendered bold...!)

       I made the same logical change to the other four for consistency,
       though they didn't seem to suffer from the same problem.

       p4dti/index.html still doesn't render right under Netscape 6.2,
       but it's from a different patterns and I couldn't see a quick
       clean fix... so I didn't mess with it for now.
#7 1046 rmg Add "P4Package" (Java Perforce API bindings) from David Markley to the //public roadmap.
#6 968 rmg Change mail addresses from "info@perforce.com" to "opensource@perforce.com"
(now that the "opensource" address exists).
#5 780 rmg Take 2 for the p4db -> p4web conversion.
(change 788 redux)
#4 779 rmg Back out change 778.
#3 778 rmg Covert all p4db links into p4web links.
#2 177 Laura Wingerd Fix link on API index page.
#1 156 Laura Wingerd Publish Mike Meyer's Python interface to Perforce API.
//guest/laura_wingerd/perforce/api/index.html
#1 155 Laura Wingerd Web page for contributed API interfaces.