--- bookie/www/index.html 2000/11/27 02:00:42 1.4
+++ bookie/www/index.html 2003/01/13 09:06:07 1.35
@@ -1,61 +1,62 @@
-Bookie is a personal attempt to keep the bookmarks that I have at home
-synced with the bookmarks I have at work, and a way of solving my
-frustrations in sharing bookmarks with other people over computers. It also
-is an outgrowth of the bluesky good
-bookmarking and collaborative
-bookmark indexing. In addition, there are sites which attack this
-problem from another angle: Bookmarker and UrlMonitor.
-
-

Quite frankly, bookmark management sucks. Every person I know has a
-collection of bookmarks which have grown over months if not years. Not only
-the bookmarks themselves but the structure of the bookmark directory is
-critical. Yahoo's origin and real, underlying purpose is as a huge
-collection of well organized bookmarks. Yet while it is easy to send a URL
-over the web, sending branches or entire trees is impossible. It is
-impossible to share the same bookmarks folder with several people, so that
-all information can be synced over a department. And it's really hard to
-keep bookmarks synced between several locations.
-
-

The roaming access feature in Netscape goes in the right direction of
-solving these problems, but RDF is the perfect answer to these problems.
-Whenever a browser wants to see bookmarks, it can make a request to a
-central bookmark server, and receive streamed RDF. Likewise, whenever a
-bookmark or branch is submitted, RDF can be sent to the server and synced
-with all the other clients.
-
-

Most of the work is already done -- Mozilla already has an
-RDFXMLDataSource, and all that needs to be done on the client end is some
-work to hook it into the network layer, and a way to present that data as a
-treeview.
-
-

The more involved work is in writing a server which can parse RDF,
-construct an internal RDF graph, and can convert the internal RDF graph into
-an SQL database. And writing it out the other way.
-
- serialized RDF RDF graph SQL database
-
-

Of course, this is barely scratching the surface of what Bookie could do
--- it could invalidate useless bookmarks, keep a cache of bookmarks for
-you... it could keep private bookmark folders which you could only see by
-typing a password... It could provide folders with multiple parents so that
-you could have the equivalent of symlinks in folders... It could rearrange
-or delete bookmarks according to your own criteria (popularity, last
-updated)... You could have limited access to bookie allowing you to add only
-annotations to a bookmark, or submit links on an honor system so that the
-most popular float to the top... You could adjust your filter so that only
-the oldest or the newest bookmarks show up.
-
-

Anyway...
-
-

The server is done, although it still is read-only. You can import
-bookmarks into the database and you can read bookmarks out of the server.
-The mozilla client will connect to the server, but I've had some troubles
-getting the RDF from the server synced up with the user interface. There's
-also a client written in Swing which I'm using for debugging, which is
-teaching me the joys of asynchronous non-blocking network IO in Java.
-
+You can read what Bookie is here, but here's the
+long and short of it:
+

Bookie is an application which keeps all your bookmarks on a central
+server so that you can access bookmarks from anywhere on the web.

+
+

The server is written in Java, and uses XML-RPC to communicate to clients.
+There's also a client written in Swing, which is pretty functional. The current
+goal is to get the Mozilla client back into shape given the existence of
+a working server (finally!)

+
+

To get the server running on your machine, download the server.zip file
+here. You should
+start the server with
+java -Dlog4j.configuration=info.xml -jar server.jar
+in a directory for Bookie usage. No database is required, as Bookie will
+create its own database if it doesn't find one. It will start on port 9000
+by default, but you can specify the port on the command line. JDK 1.4 with the
+-server option is recommended, as the I/O performance is MUCH
+faster than 1.3.1.

+
+

To get the java client running, download the client.zip file here. Unzip the client in a new directory, and execute it with one of the scripts or java -jar client.jar.
+
+

When the client starts up, it will present you with a connections box:
+

+

+

+

Create a new connection to http://localhost:9000.

+

Double click on the connection to connect to the server.

+

When the server asks you if you would like to be registered for the
+server, say yes.

+

Click on the root folder, then click on the File menu and select the
+import menu item.

Or, if you are using Internet Explorer, you can import your bookmarks by going
+ to "C:\Documents and Settings\Will Sargent\Favorites" and importing the favorites from there.

+

You can also export to Netscape if you want to get bookmarks out of the server.

+

That's it!

+

+
+

+

There is an example bookmark server at
+http://tersesystems.com. To connect
+to the test server, please enter
+http://tersesystems.com:9000/
+as your URL. Please do not use a normal password:
+most of Bookie's traffic is not encrypted, and you may be vulnerable to
+packet sniffing. Also note that there is no expectation of privacy on this
+server. Although I intend to keep all bookmark information private, I reserve
+the right to look at any and all data on the server for debugging purposes.
+

+
+

Suggestions and comments are welcome. If you have any problems with the
+above instructions, please e-mail me at the address below.