[Development] QFileSystemWatcher and Recursive Monitoring

Sylvain Pointeau sylvain.pointeau at gmail.com
Tue Jul 24 12:09:50 CEST 2012


It will only be inefficient for the few platforms that don't support the
> functionality. The cost for platforms that already do provide the
> functionality is zero.
>
> Filesystem notifications are a pretty basic piece of functionality, and
> having them be 100% cross platform would be a huge win for Qt.
>
having them inefficient is worst than not having them.
make a separate lib or class and let the user decide if he can use it.
don't force everybody to be penalized.

As I said, a generic implementation cannot beat specialized code for the
specific domain/case.

>
> > Maybe create a separate to provide a helper of creating a snapshot? In
> this case I would suggest using a sqlite database and not the memory.
> Memory is definitly a showstopper.
> >
>
> Theoretically it could be either (user chooses memory or sqlite) or both
> (fixed size memory cache with sqlite storing the rest) or neither (when the
> user wants to maintain the snapshot themselves (but remember, this is only
> applicable to the platforms that DON'T support fine grained fs event
> notifications. All these options are n/a to the platforms that do) because
> they can perform context sensitive optimizations as you mentioned)... but
> uhh I'm willing to bet sqlite would be a lot slower since now there's a hdd
> read/write. Would save memory though if that's your concern. It's just
> added design complexity which I'm guessing regedit doesn't want to deal
> with. It's already getting complex enough.
>
> Can any Qt devs comment on whether QFsw would even be allowed in Qt in a
> non cross-platform state (ignoring the fact that pretty much any solution
> is better than the current Qt release's solution lol)? regedit, you might
> find it doesn't pass code review... but maybe the capabilities() hack is
> enough, idk (i still wouldn't recommend it)...
>

Please go for it as a separate lib/class, the users will decide if this is
efficient enough to be usable.
Anyway we can implement the single signal notification, and see if your
implementation is robust, fast, and using only few memory, to be
implemented directly in the FSW.




>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120724/a4544803/attachment.html>


More information about the Development mailing list