Thank you. I could calculate the file hash and use that as the Etag, but I would need to read the file once (in chunks) to calculate the hash, and then again to send it to the client. Or I could store the entire file in memory after calculating the hash, and send it to the client without reading it again. But the process could run out of memory if I do that. So is it better to read from disk twice? Or is it better to read once and risk running out of memory.
There is one other option, and that is to add a two second delay before retrieving the time modified, but then who can guarantee that the file was not changed in that two second window. I use Malwarebytes Premium, and so far I have not had problems. But I hardly ever edit single file wikis either. Mostly just data folders, which just overwrite without checking since the state is stored in the Node process. If anyone else has any additional information or test results, or ideas, feel free to comment. Arlen On Mon, Oct 23, 2017 at 2:39 AM, Anders Jonsson < [email protected]> wrote: > Hi! > > Using the 2.0.8-nexe I get the following message when the 412 error occurs > (which for me is after something like 40-50 auto-saves): > > 412 ifmatch "1125899906846851-2837220-1508737720000" > 412 etag "1125899906846851-2837220-1508737721000" > 412 caused by difference in modified > > (Regarding antivirus programs I get the error with "normal" settings, but > so far I haven't been able to produce this error when _testing_ with > "real-time protection" completely turned off...) > > //Anders > > On Thursday, October 19, 2017 at 2:46:22 PM UTC+2, Arlen Beiler wrote: >> >> The best that I can figure is that it is some kind of problem on the file >> system. But I don't know which of two problems it is. Either it is because >> of the inode, or because of the modified time. >> >> I made a new release which will give more info about the 412 error in the >> node console when it happens. You can download it from here: >> https://github.com/Arlen22/TiddlyServer/releases/tag/2.0.8 >> >> Use the TiddlyServer-2.0.8-nexe zips. As always, when upgrading, unzip >> the folder and copy the settings.json file into it rather than copying the >> files into your old folder. >> >> Arlen >> >> -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/tiddlywiki/67da6daa-28d0-463c-bc15-a085792c579a%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/67da6daa-28d0-463c-bc15-a085792c579a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSsyw%2Bw90ccxx-esgyq%3DMutcWZZhMst2t%2BwPF0RAQXbDA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
