Uptime = 21 hours.  Multiple TWs served, edited, saved.  

No glitches.  

I think you done gone cracked it ;)



On Friday, November 3, 2017 at 3:10:41 PM UTC-5, Arlen Beiler wrote:
>
> Correct.
>
> No fingers crossed, I wrote the code. If you still get the 412 with 
> etag:"disabled", that's a bug, not a feature :)
>
> Enjoy, 
> Arlen
>
> On Fri, Nov 3, 2017 at 1:06 PM, coda coder <codacoder...@outlook.com 
> <javascript:>> wrote:
>
>> Cool. Thanks Arlen. It's up an running now - fingers crossed.
>>
>> I've added:
>>
>>   "etag": "disabled",
>>   "etagWindow": 0,
>>
>>
>>
>> to my settings.  I guess the value of etagWindow doesn't matter when etag 
>> is disabled - right?
>>
>>
>>
>> On Friday, November 3, 2017 at 11:28:59 AM UTC-5, Arlen Beiler wrote:
>>>
>>> Ok, I've added this feature to master and updated the readme.
>>>
>>> I don't have time for another release right now, so just download or 
>>> clone master, and then copy your settings.json file and the tiddlywiki 
>>> folder from your old version into master. 
>>>
>>> If you were using the nexe version, just copy node.exe in from somewhere 
>>> else if you don't want to install it globally and you'll be good to go. 
>>>
>>> You can download the the node.exe from NodeJS.org. See my notes about a 
>>> portable install in the installation instructions.
>>>
>>>
>>>
>>> On Oct 28, 2017 12:15 AM, "coda coder" <codacoder...@outlook.com> wrote:
>>>
>>>
>>>
>>> On Friday, October 27, 2017 at 8:37:44 PM UTC-5, Arlen Beiler wrote:
>>>>
>>>> The time window would work something like this. 
>>>>
>>>> Let's say you have the wiki open in one tab and you do some editing and 
>>>> the changes get saved. Can you open it in another tab or window or on 
>>>> another computer, and make some changes there. Then you come back to the 
>>>> first computer or tab and without thinking you make some changes and they 
>>>> automatically get saved. If neither the backup feature nor Etag is 
>>>> enabled, 
>>>> your changes are irretrievable lost, unless your backup system already 
>>>> grabbed them as soon as they were written.
>>>>
>>>
>>> That's identical behavior to current single-file TWs. Anyone using 
>>> single-file TWs knows (or should know) how that works.  Arlen, seriously, I 
>>> admire you trying to solve it, but the etag system is, at times, failing 
>>> you. Because the etag system is failing you, *your* system, TS, is 
>>> suffering as a result.
>>>
>>>
>>>> The backup feature of TiddlyServer lets you retrieve that old version, 
>>>> and the e-tag prevents it from being overwritten in the first place. 
>>>>
>>>> Now if I would put a time window in place of, say, 10 seconds, it would 
>>>> be able to save only if the file on disk is nor more than 10 seconds newer 
>>>> than the version loaded in the browser. If it was modified more than 10 
>>>> seconds later than the version in the browser it would not be able to 
>>>> save. 
>>>> This would be a setting in settings.json so the user could adjust it 
>>>> according to the need. 
>>>>
>>>
>>> Nifty idea.  But again, it's not needed, IMO.  You're trying to fix an 
>>> etag issue, not a TS issue, per se.
>>>  
>>>
>>>>
>>>> Interesting thought, I will consider it. 
>>>>
>>>>
>>> Are you referring to my *bloody-minded* "A PUT request is an undeniable 
>>> request..." statement?  Having thought about it more, I'd go even further 
>>> -- refusing to let me save, implies the server knows better than I do what 
>>> needs to be (and should be allowed to be) saved.  That's a showstopper, for 
>>> me. :/
>>>
>>> Anyway, I admire your diligence on this but hope you give me switch 
>>> like...
>>>
>>> {
>>>   ...
>>>   "ts-options" : {
>>>     "enable-etag": false // default true
>>>   }
>>> }
>>>
>>>  :)
>>>
>>>
>>> -- 
>>> 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 tiddlywiki+...@googlegroups.com.
>>> To post to this group, send email to tiddl...@googlegroups.com.
>>> 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/5c54e6a5-87fc-44cd-8b97-dcb2dcc10366%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/tiddlywiki/5c54e6a5-87fc-44cd-8b97-dcb2dcc10366%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 tiddlywiki+...@googlegroups.com <javascript:>.
>> To post to this group, send email to tiddl...@googlegroups.com 
>> <javascript:>.
>> 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/9a7f8227-6558-4779-bc88-a777ad72fde4%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/9a7f8227-6558-4779-bc88-a777ad72fde4%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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
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/8da6d352-fffb-4629-9345-ba92a7bd2fb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to