Re: Publishing HTML

[Colm Smyth <Colm Smyth Sun COM>]

Hi Dan,

I was suggesting that a help-server could create and manage a shared (among
multiple users) cache of render-ready documents; the help-server generates
render-ready (e.g.  html) documents on demand or serves them via it's cache.
Since no user process needs to write to the cache, there is no security issue.
Help-server is probably a bad name; document server might be better.

The help/doc-server could either permit direct read access to the cache, or
simply serve up documents like a traditional web server, over http.  If we go
with the web server route, there are many open-source web-servers, we would
simply create a backend (cgi, servlet, ...)  to generate the render-ready
document format (html) and manage a cache.

For browser clients, the browser cache could provide local per-user speed-up
for web format (html, pdf, etc.) document access.

Colm.

>X-Authentication-Warning: enlightenment.uchicago.edu: dmueth owned process 
doing -bs
>From: Dan Mueth <d-mueth uchicago edu>
>X-Sender: <dmueth enlightenment uchicago edu>
>To: Colm Smyth <Colm Smyth Sun COM>
>cc: GNOME Doc List <gnome-doc-list gnome org>
>Subject: Re: Publishing HTML
>MIME-Version: 1.0
>
>
>On Tue, 26 Jun 2001, Colm Smyth wrote:
>
>> - a help server could solve the problem of security with a multi-user
>>   cache; making it a http server (that serves html) could allow a
>>   regular browser to view help; it also would allow regular kinds of
>>   http cache (browser or http proxy); lastly it allows regular kinds of
>>   bookmarking for favourite help items
>
>By "multi-user cache", do you mean a seperate cache for each user?  That
>should avoid the security problems associated with a shared cache.
>
>Dan
>