Reply to thread

Message

<blockquote data-quote="zeflash" data-source="post: 146578" data-attributes="member: 13641">Hi everyone, I see this project is still alive (maybe I'll try to get back in at some point ... I don't really have much time these days).About the shared DB, I did some tested locally (being able to select a shared drive to host the DB, put the banner folders relative to this file) in order to have simultaneous access to it.Sadly it's not working well at all. First problem is performance issues; even though I'm on a gigabit network, it takes 10 times longer to display the tree architecture on the setup part of the plugin when the DB is on a network. It's a bit less visible while inside MP, but still painfully slower than with a local DB.Second problem, which is much worse, is that I was getting corruption in the DB (reason unknown, but I'm guessing network failures translating to failed write operations). So at some point, the DB is busted and has to be recreated from scratch, which kinda misses the whole point.So, IMO this way of doing it is a dead end. Now, the thing is, the only interesting part here is to share the viewed flag. Nothing prevents us from storing this flag outside of the DB, as a file along the series. That's probably what I'll do next, whenever I'll manage to find some free time (for coding, which isn't the priority anymore now!)</blockquote>

[QUOTE="zeflash, post: 146578, member: 13641"] Hi everyone, I see this project is still alive (maybe I'll try to get back in at some point ... I don't really have much time these days). About the shared DB, I did some tested locally (being able to select a shared drive to host the DB, put the banner folders relative to this file) in order to have simultaneous access to it. Sadly it's not working well at all. First problem is performance issues; even though I'm on a gigabit network, it takes 10 times longer to display the tree architecture on the setup part of the plugin when the DB is on a network. It's a bit less visible while inside MP, but still painfully slower than with a local DB. Second problem, which is much worse, is that I was getting corruption in the DB (reason unknown, but I'm guessing network failures translating to failed write operations). So at some point, the DB is busted and has to be recreated from scratch, which kinda misses the whole point. So, IMO this way of doing it is a dead end. Now, the thing is, the only interesting part here is to share the viewed flag. Nothing prevents us from storing this flag outside of the DB, as a file along the series. That's probably what I'll do next, whenever I'll manage to find some free time (for coding, which isn't the priority anymore now!) [/QUOTE]

Verification