← Back to team overview

zim-wiki team mailing list archive

Re: Restart for changes (Web Server Crashes - no)

 

Looks like a bug in the caching to me - will look into that. Could you
report it in the bug tracker?

The expected behavior is that the webserver sees all page changes after a
page is safed and the browser is refreshed. (Which makes me think - is
there a use case for a web template that forces reloading every x seconds
from javascript ?)

Thanks,

Jaap



On Fri, Feb 20, 2015 at 11:49 PM, Mike Morris <mike@xxxxxxxxxxxxxx> 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
>
>
>
>
>
>
>> Regards,
>>
>>      Andreas
>>
>>
>>
>> On 18.02.2015 21:55, Mike Morris wrote:
>>
>>> On 02/18/2015 12:45 PM, Mike Morris wrote:
>>>
>>>> However, when I update a document it crashes the webserver. Upon
>>>> restarting the webserver, the changes are available on the webpage.
>>>>
>>> Sorry - the webserver "crash" was apparently another problem, I can't
>>> get it to repeat today.
>>>
>>> But updates do not propagate to the running webserver.... so I'm still
>>> wondering if requiring a webserver restart to update the browser  is
>>> intended behavior.
>>>
>>> Thanks
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~zim-wiki
>>> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~zim-wiki
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~zim-wiki
> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References