kio and frameworks 5

[Casper Clemence]

On 13 May 2012 11:58, David Faure <faure at kde.org> wrote:
>
> On Sunday 13 May 2012 11:32:46 Casper Clemence wrote:
> > * it mounts lots more than an ordinary VFS - including XML documents (so
> > the tree of the document can be browsed), databases, X (so that window
> > position and size for example can be read and modified as if they were
> > data
> > in the filesystem), web browser bookmarks...
> > .. all of which leads to the "uniform method of access" I mentioned
> > where
> > all sorts of document data, document structure and metadata becomes
> > available in a a uniform way.
>
> All this sounds synchronous (the data is always available right away).
> So it probably makes sense as a kioslave (so that all applications can
> access
> all of the above via KIO API), not as a replacement for KIO (which has to
> provide an asynchronous way of accessing network protocols).
>
> --
> David Faure, faure at kde.org, http://www.davidfaure.fr
> Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5
>

libferris handles asynchronous IO including network protocols.

I don't want this to turn into me arguing that libferris
_should_defineately_replace_kio_ I really don't know enough about
either to do that.

A kio slave for libferris could be created.

I am wrong but I think that the interesting access and indexing that
libferris provides for metadata would serve KDE better if it were
integrated at the level of KIO rather than as a kio-slave.

I really urge any of you to have a quick look though some of the
feature descriptions and papers on the libferris site
http://www.libferris.com/ and some of the demos on Ben's blog
http://monkeyiq.blogspot.co.uk/ to get an idea of the fun things it
makes possible.

I would like to give a deeper answer but laptop battery is about to die....