On Fri, Jun 24, 2011 at 9:41 AM, Vishesh Handa <[email protected]> wrote:
> > > On Fri, Jun 24, 2011 at 7:07 PM, Nathan Bradshaw < > [email protected]> wrote: > >> On Thu, Jun 23, 2011 at 5:51 PM, Thomas Lübking < >> [email protected]> wrote: >> >>> Am Thursday 23 June 2011 schrieb Steven Sroka: >>> > What is the best way for a KDE program to store data? Not passwords or >>> > anything sensitive, but data a user had typed into text fields. >>> > >>> > Some sort of database. Something along the lines of KConfig or KConfig >>> > XT but for raw data not configuartion data for programs. >>> Depends on the type of data and what you want to do with it. >>> >>> If you want to "dump memory", you need to serialize the data. >>> Have a look at QDataStream. >>> >>> KSharedDataCache helps to to access information from several processes at >>> the >>> same time (like eg. the icons) and save memory. >>> >>> Also you can write it to some xml or an kconfig/qsettings ini-a-like file >>> with >>> the advance of "less" access ;-) >>> >> >> Is RDF through Soprano an option here? >> > > Yes. But you don't really want to another another virtuoso instance. You > could use another backend though. > > If you can structure the data properly, you could store it in Nepomuk's > virtuoso repository. > So the instance of virtuoso running for nepomuk can't be shared? That would be a bit of an onion in the ointment. I guess going away from an RDF store, there is sqlite if you don't mind the dependency.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
