piggy-bank installation in two pieces

From: Leo Sauermann <sauermann_at_dfki.uni-kl.de>
Date: Fri, 16 Dec 2005 15:19:56 +0100

Hello simile,

Last week there was the discussion about gunnar's memory
leak/performance bug and Stefano and I had an ongoing e-mail chat about
delivering piggy-bank in two pieces.

Es begab sich aber zu der Zeit 12.12.2005 16:13, da Stefano Mazzocchi

> Even a better solution would be to rewrite some internals to
> completely decouple the browsing experience from the invocation of the
> java subsystem and I think I might try to do that as well since it
> also makes it easier to separate Piggy Bank in two: a local server
> that runs independently and on its own process (thus reducing the
> fragility of the browser process) and a much smaller browser extension
> that does not contain any java code.
> The issue, and we already talked about it between us, at that point
> would be to make the installation and deliver of such local service as
> easy if not easier than Piggy Bank already is.
> What do you people think?
 From the Semantic Desktop perspective, we would like to have loosely
coupled services anyway. The piggy-bank browser plugin in mozilla is the
place to be for scraping pages and browsing local RDF data. But the
storage of RDF and the larger Sesame-depending parts in Java may be
better placed into a "rdf store service".

The background from the Semantic Desktop view is that other applications
like www.gnowsis.org or Haystack (or IRIS[2]) may want to use the
piggy-bank data - and vice versa. Piggy-bank would benefit from
accessing data stored inside the gnowsis store. Background info: one
part of gnowsis is a local RDF store with addresses from MS-Outlook,
file-metadata from the filesystem, etc.

I suggested here [1] to have a kind of "Semantic Bus" on your desktop
computer, where services can meet. In our case (gnowsis and piggy-bank)
it can be very simple: there are a couple of applications that use
Sesame-like storage and cooperate using the sesame interfaces.

But now the braking problem, mentioned by Stefano, was that faceted
browsing (in piggy-bank/longwell) takes about 30 sesame requests to
gather the data for one page - a time-consuming process of 30 requests
handled over tcp/ip and web protocols.

In gnowsis we bundle the calls into SPARQL DESCRIBE/URIQA calls and
that's enough to visualize, one call to browse one resource, but there
is no faceted browsing in gnowsis. Although in gnowsis we also not
seperate DB and gui.

So, I would be happy to seperate the sesame database from the XPI
plugin, but how to do this with good performance?


[1] http://leobard.twoday.net/stories/1214653/
[2] http://www.openiris.org/

DI Leo Sauermann       http://www.dfki.de/~sauermann
P.O. Box 2080          Fon:   +49 631 205-3503
67608 Kaiserslautern    
Germany                Mail:  leo.sauermann_at_dfki.de
Received on Fri Dec 16 2005 - 14:13:14 EST

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:39:18 EDT