Diff for /bookie/www/setup.html between versions 1.4 and 1.12

version 1.4, 2001/03/26 07:55:31 version 1.12, 2002/07/14 09:36:35
Line 1 Line 1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Setup instructions for Bookie.<html>
<p><head>
If you're just browsing or don't need to edit files directly, you can look  <title></title>
at Bookie through the <a</head>
href="http://www.mozdev.org/source/browse/bookie/">web interface</a>.<body>
<p>Setup instructions for compiling and running Bookie: 
If you want to contribute to Bookie or compile it, then you should grab a<p>If you're just browsing or don't need to edit files directly, you can
CVS <a href="http://www.cvshome.com">client</a> and set up a workspace for bookie.look at Bookie through the <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
You download bookie by doing this (you only need to login once, the passworda CVS <a href="http://www.cvshome.com">client</a> and set up a workspace
is guest).for bookie.</p>
<p>You download bookie by doing this (you only need to login once, the password
<pre>is guest).  Please use the prune option when checking out and updating, since
 cvs -d :pserver:guest@mozdev.org:/cvs loginthe CVS tree has a lot of dead branches in it.</p>
 cvs -d :pserver:guest@mozdev.org:/cvs co bookie<pre> cvs -d :pserver:guest@mozdev.org:/cvs login<br> cvs -d :pserver:guest@mozdev.org:/cvs co bookie -P<br></pre>
</pre><p>The java client is in <code>/clients/swing</code>.  There is an<a
 href="http://jakarta.apache.org/ant">ant</a> script that should compile everything.
<p>The database needs data in order to work.  I wrote /scripts/import.pl which The client depends on Jena, Apache XML-RPC, Log4J and Xerces. All the libraries
takes in my bookmarks.html file from Netscape and pumps it into theshould be available in lib.  The client's main class is<code>com.tersesystems.bookie.client.Client</code>.
database.  It actually relies on a couple of non-standard modules which you Downloading<a href="http://tersesystems.com/bookie/client.jar">client.jar</a>
may need to download from ActivePerl or CPAN.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>You need to have a database set up with a database schema.  Look in href="http://jakarta.apache.org/ant">ant</a> script that should compile everything.
/sql/solid for an example schema.  It's not too complicated. The server currently depends on JTidy, Marquee XML-RPC,  Jisp, Servlet 2.2,
Log4J, and Xerces, which are all available in lib.  The server's main class
<p> You can start the server from the root directory with: <br>is <code>com.tersesystems.bookie.service.xmlrpc.BookieServlet</code>.</p>
<code>java bookie.xmlrpc.BookieServer -Dbookie.logging=./scripts/logging.properties<p>  The server will create four files on initialization in the current directory:
-Dbookie.database=./scripts/database.properties</code><br>  </p>
<ul>
<p>There's an Ant script in ./scripts/ which handles compilation and testing.    <li>profile.db - a database of profile information.</li>
    <li>profile.idx - an index of profile.db</li>
<p>Right now, the only way you get useful data is with the test class    <li>bookmarks.db - a database of bookmarks information.</li>
<code>ClientTest</code>, which reads in the RDF to a memory model and writes    <li>bookmarks.idx - an index of bookmarks.db</li>
out the answer to some queries (like 'what children does the root node  
have?').  More is on the way.</ul>
  These databases contain all the information needed for the server to work.
Will. 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
   from different servers.  However, care should be taken with this feature,
   as there is no facility to distribute messages between clients that a  
  branch has been deleted.  </p>
 <p>  Bookmarks are cached on the server, but since bookmarks are unique to
   each client this isn't that much of a win.  Performance seems okay for
 now    (and if anything seems bound on the XML    processing and IO overhead).
  Database operations are not transactional.</p>
 <p>  The server uses an MD5 hashed password for authentication of the client.
   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.4  
changed lines
  Added in v.1.12


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