Diff for /bookie/www/setup.html between versions 1.13 and 1.14

version 1.13, 2003/02/08 21:18:05 version 1.14, 2003/04/14 07:42:47
Line 1 Line 1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">Setup instructions for compiling and running Bookie:
<html><p>If you're just browsing or don't need to edit files directly, you
<head>can look at Bookie through the <a
  <title></title> 
</head> 
<body> 
Setup instructions for compiling and running Bookie:  
<p>If you're just browsing or don't need to edit files directly, you can 
look at Bookie through the <a 
  href="http://www.mozdev.org/source/browse/bookie/">web interface</a>. </p>   href="http://www.mozdev.org/source/browse/bookie/">web interface</a>. </p>
<p>If you want to contribute to Bookie or compile it, then you should grab<p>If you want to contribute to Bookie or compile it, then you should
a CVS <a href="http://www.cvshome.com">client</a> and set up a workspacegrab a CVS <a href="http://www.cvshome.com">client</a> and set up a
for bookie.</p>workspace for bookie.</p>
<p>You download bookie by doing this (you only need to login once, the password<p>You download bookie by doing this (you only need to login once, the
is guest).  Please use the prune option when checking out and updating, sincepassword is guest).  Please use the prune option when checking out and
the CVS tree has a lot of dead branches in it.</p>updating, since the CVS tree has a lot of dead branches in it.</p>
<code> cvs -d :pserver:guest@mozdev.org:/cvs login<br></code><code> cvs -d :pserver:guest@mozdev.org:/cvs login <br>
<code>cvs -d :pserver:guest@mozdev.org:/cvs co bookie<br></code></code> <code>cvs -d :pserver:guest@mozdev.org:/cvs co bookie -dP<br>
<p>The java client is in <code>/clients/swing</code>.  There is an<a</code>
 href="http://jakarta.apache.org/ant">ant</a> script that should compile everything.<p>The java client is in <code>/clients/swing</code>.  There is an <a
 The client depends on Jena, Apache XML-RPC, Log4J and Xerces. All the libraries href="http://jakarta.apache.org/ant">ant</a> script that should compile
should be available in lib.  The client's main class is<code>com.tersesystems.bookie.client.Client</code>.everything.&nbsp; The client's main class is <code>com.tersesystems.bookie.client.Client</code>.<br>
 Downloading<a href="http://tersesystems.com/bookie/client.jar">client.jar</a></p>
will give you the classes, source code and javadoc to play with.</p><p>The java server is in <code>/server</code>.  Again, the <a
<p>The java server is in <code>/server</code>.  Again, the<a href="http://jakarta.apache.org/ant">ant</a> script that should compile
 href="http://jakarta.apache.org/ant">ant</a> script that should compile everything.everything.  The server's main class is <code>com.tersesystems.bookie.service.xmlrpc.BookieServlet</code>.</p>
 The server currently depends on JTidy, Marquee XML-RPC,  Jisp, Servlet 2.2,<p> The server will create four files on initialization in the current
Log4J, and Xerces, which are all available in lib.  The server's main classdirectory: </p>
is <code>com.tersesystems.bookie.service.xmlrpc.BookieServlet</code>.</p> 
<p>  The server will create four files on initialization in the current directory: 
  </p> 
 <ul>  <ul>
    <li>profile.db - a database of profile information.</li>  <li>profile.db - a database of profile information.</li>
    <li>profile.idx - an index of profile.db</li>  <li>profile.idx - an index of profile.db</li>
    <li>bookmarks.db - a database of bookmarks information.</li>  <li>bookmarks.db - a database of bookmarks information.</li>
    <li>bookmarks.idx - an index of bookmarks.db</li>  <li>bookmarks.idx - an index of bookmarks.db</li>
   
 </ul>  </ul>
  These databases contain all the information needed for the server to work.These databases contain all the information needed for the server to
 Deleting   these files will cause the server to start off fresh. work.  Deleting   these files will cause the server to start off fresh.
<p>  The server does not attempt to limit multiple logins on the same account<p> </p>
  from different servers.  However, care should be taken with this feature,<p> Bookmarks are cached on the server, but since bookmarks are unique
  as there is no facility to distribute messages between clients that a  to   each client this isn't that much of a win.  Performance seems okay
 branch has been deleted.  </p>for now    (and if anything seems bound on the XML    processing and IO
<p>  Bookmarks are cached on the server, but since bookmarks are unique tooverhead).  Database operations are not transactional.<br>
  each client this isn't that much of a win.  Performance seems okay for</p>
now    (and if anything seems bound on the XML    processing and IO overhead).<p>Please e-mail me at <a href="mailto:will_sargent@yahoo.com">will_sargent@yahoo.com</a>
 Database operations are not transactional.</p>if you have any problems.<br>
<p>  The server uses an MD5 hashed password for authentication of the client.</p>
  Once authenticated, the server maintains a session based off the IP address 
  of the client.  All data is sent in the clear, and as such the passwords 
and   XML-RPC information may be    <a 
 href="http://www.robertgraham.com/pubs/sniffing-faq.html">packet sniffed</a>. 
  Even if the attacker does not know   the clear-text password, he can still 
send the MD5 hash to be authenticated as   the user.  Unfortunately, XML-RPC 
does not cover    <a 
 href="http://www.strongsec.com/tutorials/security.htm">security</a> and 
session management   very well; if there are any new RFCs I would love to 
hear about them.  One   possible RFC is <a 
 href="http://jimfl.tensegrity.net">Jim Flanagan's</a>    <a 
 href="http://jimfl.tensegrity.net/xmlrpc/">proposal</a>, but this requires 
  the use of <a href="http://www.ietf.org/rfc/rfc2617.txt">HTTP digest   
 authentication</a>, which I believe most clients don't support.</p> 
<br> 
</body> 
</html> 

Removed from v.1.13  
changed lines
  Added in v.1.14


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>