|
ok guys, well stopping and restarting calibre is working a workaround,I guess that closing the main program stops and restarts the content server., and only take s a couple of seconds
and doing that, but doing only that would disprove that windows network caching is to blame ?
it seems poor design that content server cannot be trusted to server the latest version, always ?
and yet I probably could use connect as wireless device, I forget exactly why I chose not to do that, standardly. Probably because I only wanted the one way calibre-> device delivery.
i never read in server.
i connect to server, get book onto device, via calibre companion; disconnect, then read on device.
what I'd like is some definitive explanation of what is happening, is it a feature or a bug, and is it documented somewhere that I have not looked. i TRIED SEARCHING THE FORUM FOR CONTENT SERVER CACHE BUT NO JOY THERE.
e.g. is only the last book served cached, or the last n books, or the last x minutes ???
|