Hi Danielo It's hard for me to run your code right now, so I'm going to need some help figuring out what's going on.
Can you show a log of the requests that you're seeing between the browser and the server? Exactly what tiddlers are being transferred? What actions are you taking in the user interface? > Another think I can not understand is that, once one tiddler have been fetched from the server, that particular tiddler is requested on every query cycle, even it is unchanged, why? Why not check the version or the modified date and only ask for it if it has changed? That's definitely not how it works, but it's what would happen if the skinny tiddler listing was showing a more recent revision number than when the tiddler was requested. Best wishes Jeremy. On Tue, May 19, 2015 at 10:35 AM, Danielo Rodríguez <[email protected]> wrote: > >> Can you give the steps needed to reproduce the behaviour that you're >> seeing? Ideally, those steps would involve running ./bin/serve.sh in the >> master branch of the repo. Or are you describing behaviour that you're >> seeing with a custom syncadaptor? If so, it might be helpful for me to see >> the code, >> >> > Hello Jeremy. Yes, I'm talking about a custom syncadaptor. You can see it > here > > https://github.com/danielo515/couchadaptor/blob/master/couchdbadaptor.js > > I though the fetching part was done by the TW core and the syncadaptor > only provides an interface to talk to the server. > -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 http://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/CAPKKYJaxTqO%2BamDXpRk0W%3DoSj7bc7f6RGWmYcjwkzQOqDN5y6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
