Hi, On Sat, Sep 24, 2011 at 11:48 PM, Иван Комиссаров <[email protected]> wrote: > Second - if we provide new API, should it be synchronous (like QFile) or > asynchronous (like Q*Socket)?
My personal thoughts would be to drop the synchronous like a brick, because if it exists, people who don't know any better *will* (ab)use it because it's "easier" or simply because examples/other people do and they don't know what that really means, and then you end up with poorly-performing applications. At least, that's the experience I've had with watching people write applications using the Qt Mobility Contacts API - it has an asynchronous API, but the synchronous one gets used a lot without thought, until it turns out to be the cause of a performance problem after some analysis. Plus a great deal of the things you'd probably want VFS backends for are going to be asynchronous, anyway. BR, Robin _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
