Saving to a remote machine (Confirm changes to this tiddler VS Save changes)

[Panos Firbas]

Hi TWdev,     

      

I am serving a TW from a vps machine with the little python script that we made in the TWgroup here.       

       

I had been interacting with the server from a nice connection, but now that I returned home to my horribly slow connection (think.. 300kbps down, 100kbps up),       

I am noticing that the whole thing is quite slow. So here's the questions:       

          

Do I understand right that whenever a PUT request is made, the entire TW (2Mb for the empty.html) is sent to the server? (Firefox dev tools net inspector says 2Mb transfered over 21 seconds).       

         

If so, is there any difference between the two (as far as I can tell) save buttons (the one in the new/edited tiddler "Confirm changes to this tiddler" and the global one "Save changes") ?          

       

Can I detect this difference server-side in the request? I'm not too familiar with html requests and a quick snooping of the python object didn't yield any results..       

        

Can I avoid saving in the server when I edit a tiddler and only manually save when I hit the 'global' red button ?      

  

[Mohammad]

Hi Panos,

I am not an expert in the field you asked. Jeremy, Jed, and Arlen have developed server client tools.

But as I know the save changes saves the whole wiki in a single html file even on node.js

Normally save a tiddler on those tools (node.js) only save the tiddler.

--Mohammad

[Mohammad]

Email readers: post edited

[TonyM]

Panos,

Extending what Mohammad says, if you have autosave on, the saving of one tiddler (into browser memory) triggers the wiki/file save. When on a node implementation it is possible for the single tiddler to be saved/committed to disk by the server, in single file mode the whole wiki must be saved each time.

With a single file wiki you can delay saving until necessary because changed tiddlers are saved in the browser memory, and there is a warning if you try and navigate away without doing the file saving, so on slower connections I trigger my own saves rather than use autosave.

Regards

Tony