Forward: Page web inacessible - Unreachable web page

[Jonas Bosson]

On Thu, 2006-02-09 at 14:32 +0100, Carsten Svaneborg wrote:
> On Thursday 09 February 2006 14:09, Jonas Bosson wrote:
> > Does anyone have any experience with this tool? (check /etc/pgpool.conf)
> I don't.
> 
> > Also, I would like to put all the text into files rather then having
> > them hogging sql-queries. Like this:
> > /home/zqex/PatData/pat/EP/122/2323.gz
> > And let the PatentView (view.py) script read directly from the files.
> 
> I have another idea: PatentView produce WIKI output from the DB, so what
> about simply creating a static read-only wiki page with the output?
> 
> Then no scripts are necessary for displaying patents, and patent comments
> will still work and perhaps it will even be usefull for purposes of using the
> wiki search functions for searching patents?
> 
> We could still keep the data in the DB. However, it becomes necessary to
> keep wiki pages in sync with the DB when patents are deleted, added,
> and updated. However, this could be done with nightly updates.
> 
> Alternatively the perl script that imports data into the patents and the 
> patentview python script could be merged to generate the wiki patent
> page directly. I once had a plan of writing a perl interface to the wiki,
> such that a perl based bot could generate pages directly in the wiki,
> but I have never gotten around to do it.
> 

I have some trouble finding dependencies. But if we move from db-centric
management, this will get a bit more complicated. We should have a code
module for patent-content-management, in perl and in python. Perhaps it
should be regarded as a cache for EP-data. It might get complicated as
the db gets less and less normalized. 

I am not sure if moin moins single directory-layout will work well.
A well structured compact format and best a good directory layout is
probably the most important issues since 75% time is spent waiting on
IO. I don't know how the optimal size of directories is selected for
exfs2 (index is turned on). Mozilla separates its cache files into sub
directories. CPU is afaik not yet a issue. 

Linux 2.6.11-1-686 (gauss)      02/09/2006

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
          14.12    0.15    6.79   74.94    0.00    4.00

/jonas