You might setup a job in a while(1)-sleep-loop (or cron job)
which exports the book periodically, say, every 10 seconds
to some location which is services by a web server (apache ..).
Drawback: You need an external web server.
Benefits: No dependency on zim application and even localhost
being up and running. There is some redundancy and persistence also.

Keep in mind that clients need to reload new pages anyway. They
should be notified about new contents, or they try on occasion.

Another idea is git. Zim works great with git and any time you
create a new version you could generate a html export with a
git hook.

Just ideas..


On 20.02.2015 23:49, Mike Morris wrote:
> On 02/18/2015 09:32 PM, WEHLER Andreas wrote:
>> Hi.
>> Web server has to be restarted for changes. You cannot watch some
>> editor typing in the keyboard with a remote web server ...
> I don't need to see the actual editing, down to keystroke level, as in a
> remote desktop session. My use case at present is working in a
> conference room with no projector; I just want other people to be able
> to see the work in progress in their browsers, refreshed every few
> seconds or minutes.
> Since Zim auto-saves on updates, would it be possible to flush the
> webserver's cache for a modified page as it does the save? Then the
> webserver would be as up to date as the disk image, which is more than
> enough for my use case.
> I assume the webserver has some kind of cache, otherwise it couldn't
> serve the pre-saved version of a page, right? I don't image there are
> many users with high enough traffic on the zim webserver that clearing
> the cache would be a big problem. But it could also be made a preference.
> Is this harder than I imagine it, or could it be a reasonable feature
> request?
> TIA,
> MikeM
Mailing list: https://launchpad.net/~zim-wiki
Post to     : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Reply via email to