HikariMemberDecember 5, 2015 at 3:54 amPost count: 7
What do u mean with Application?
The problem I see here is that they really wanna make Tabbles a shared experience. They don’t want sharing to be one of the features, they want any resource to be sharable, and sharing be normal in user’ experience.
The easiest and probably best way to do it is how they did, get a RDBMS running data and have a Tabbles WinApp running on each PC connecting to it. But it has the drawback of latency and the requirement of being always connected with the RDBMS. And also the resource needed to run the RDBMS of course.
It was a solid decision, it was implemented, and it has came to stay.
The problem with caching is how to sync data back to server, and how to merge inconsistences among clients. I mean, the advantage of a DBMS is that data is processed in transactional/atomic behavior. If 2 users try to write on the same data on the same time, the later has to wait the first finish. Writing on different areas can be done in parallel.
There are apps that support local caching, like Evernote. But then, again, there’s the trouble of implementing multiple data accesses, of implementing their synching and the merging of data, and users also most do manual merging.
For 1 user in 1 PC, I understand these drawbacks will never happen and we remain with the performance issues. But, at least for now, this is te best solution available for powerful and easy sharing support.
xkatMemberMarch 8, 2016 at 12:48 amPost count: 39
sorry for posting such ambiguous message!
i thought Andrea/Maurizio might (;) understand the (poorly worded) question because of previous communication.
nonetheless, this is about the shell extension (pop-up) tagging interface.
What i was trying to describe was the ability to cache the tabble list particularly for initial tagging (tabbling).
Thus, I expect the Tabble list wouldn’t necessarily be ‘complete’ at all times, except when after a tabble was ‘created’, ‘deleted’, or ‘re-ordered'(change hierarchy), in the main interface.
I don’t know how much memory this list would require, and it would ‘lazy-update’ whenever resources were available. The cache would be called when the ‘quick-tag’ was invoked.
btw, caches seem in place at ‘recent tags’ in the pop-up tag interface “Tag” pulldown.
AndreaKeymasterMarch 29, 2016 at 11:44 amPost count: 879
Thanks guys for the conversation – solid answer from you Hikari 🙂
Xkat: what is exactly the problem you’re looking to solve? I’m asking this while the database querying performances have been surprisingly good (and indeed, we have a good technical understanding for that and therefore we’ve been able to optimize that quite a lot), on the other the shell extensions, which was re-written by 3 different people using 3 different techniques, has proven to be unstable slow, and generally unpredictable.
Do you have issues with the shell extension(s)?
You must be logged in to reply to this topic.