Syncadaptor is asking all the time for already retrieved tiddlers

[Danielo Rodríguez]

Hello,

Before opening another github issue I want to be sure about how the syncadaptor works, because I'm not understanding it's current behavior.

It is asking for skinny tiddlers, so far so good. After that, it asks (fetch from the server) for some tiddlers, I don't know why those and not others. For example, it asks the server for $:/StoryList,$:/view and another normal tiddler. I can understand the two first request, but I can not understand why it is asking for a normal tiddler. That normal tiddler is listed in one opened tiddler, but there are other tiddlers also listed and they are not retrieved, why?

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?

thanks for any response

[Jeremy Ruston]

Hi Danielo

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,

Best wishes

Jeremy.

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
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/6ddcf64f-7538-4d8f-9f14-4cf1ba5c404f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Danielo Rodríguez]

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]

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.

[Danielo Rodríguez]

Hello Jeremy,

I found the problem. The server was not including the revision field on the skinny tiddlers. It was tricky because once the tiddler is fetched (full tiddler) the revision field was included. It was only on the skinny version were the revision field was not included.

Regards