TagLib does not use KIO

I have just posted a bug against Amarok 2.x, requesting KIO-support, and I got
this comment back:

---------------------------
That's not going to happen because TagLib does not use KIO.
---------------------------

I am not very familiar with either KIO or TagLib, but from my point of view
this does not make sense, could anyone please enlighten me? :)

The bug: http://bugs.kde.org/show_bug.cgi?id=165469
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Robert Grønning wrote:

> I have just posted a bug against Amarok 2.x, requesting KIO-support, and I got
> this comment back:
>
> ---------------------------
> That's not going to happen because TagLib does not use KIO.
> ---------------------------
>
> I am not very familiar with either KIO or TagLib, but from my point of view
> this does not make sense, could anyone please enlighten me? :)
>
> The bug: http://bugs.kde.org/show_bug.cgi?id=165469

KIO is KDE's I/O abstraction layer, mostly used for network protocols.  
TagLib doesn't, and won't in the future, use any of KDE's libraries.

-Scott
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

[Vitali Lovich]

Scott Wheeler wrote:

> Robert Grønning wrote:
>  
>> I have just posted a bug against Amarok 2.x, requesting KIO-support, and I got
>> this comment back:
>>
>> The bug: http://bugs.kde.org/show_bug.cgi?id=165469
>>    
>
> KIO is KDE's I/O abstraction layer, mostly used for network protocols.  
> TagLib doesn't, and won't in the future, use any of KDE's libraries.
>
> -Scott

Just would like to add that apparently there's a kio fuse fs, so the
problem is mitigated.
The upside to this method (although it looks non-trivial to set up), is
that you don't actually need application or library support.

http://wiki.kde.org/tiki-index.php?page=KIO+Fuse+Gateway

Actually, Amarok could probably add transparent support later by
integrating more tightly with the fuse implementation (i.e. automounting
the kio targets as necessary).  Actually a truly slick feature would be
that you could actually configure fuse plugins from Amarok and have it
access those file systems transparently (perhaps provide a mountpoint in
some private tmpfs).
_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel

Vitali Lovich wrote:

> Just would like to add that apparently there's a kio fuse fs, so the
> problem is mitigated.
> The upside to this method (although it looks non-trivial to set up), is
> that you don't actually need application or library support.
>
> http://wiki.kde.org/tiki-index.php?page=KIO+Fuse+Gateway
>
> Actually, Amarok could probably add transparent support later by
> integrating more tightly with the fuse implementation (i.e. automounting
> the kio targets as necessary).  Actually a truly slick feature would be
> that you could actually configure fuse plugins from Amarok and have it
> access those file systems transparently (perhaps provide a mountpoint in
> some private tmpfs).

I'd be interested in hearing how that works if someone tries it out.  I
suspect it would be painfully slow since KIO is stream oriented and
TagLib does a lot of random access.

-Scott

_______________________________________________
taglib-devel mailing list
taglib-devel@...
https://mail.kde.org/mailman/listinfo/taglib-devel