metakit graph storage

[Stanislav Karchebny]

On Saturday 12 February 2005 16:41, Aaron J. Seigo wrote:

> that stands well integrated and purpose built. in fact, i think it will be
> faster, more efficient and produce a better API to implement this bit
> ourselves.

Well, you are right *too*. :)

Concurrent/network access is not well inside metakit as its a one-app-library, 
but i think we will handle access to klink database through 
klink{libs,daemon} for network access anyway, or am I wrong here?

> > Since we're going to introduce metakit into kdelibs for akregator at some
> > point, it wouldn't be too much overhead to use it (its lightweight
> > anyway).
>
> into kdelibs? did i miss a discussion on kde-core-devel about this?

Nope, you didn't. We want to make it up and running first before discussing 
its pros and cons. Thats why *at some point* is written there.

-- 
keep in touch. berkus.

Roey on #kde-devel: when I hear best of breed I tune out--it's too much a 
buzzword. What I carry between my legs is best of breed. And like KDE, just 
because it's less visible doesn't mean it gets less usage.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/klink/attachments/20050212/348f9c21/attachment.pgp