Re: [Corelinux-public] Endianess

[Frank V. C. <fr...@co...>]

----- Original Message ----- >
#if Frank V. Castellucci
> > Is our persistent data (the users application data I will assume) for
> > local storing? Exchange? Both?
>
> I can offer examples from real life:
>
> 1. KDE uses a protocol called DCOP for communication. This was designed
> as a replacement for using CORBA. Parameters are marshalled by streaming
> into a 'QByteArray'. Here endianness is important.
>
> 2. Recently I created a class which gave the same functionality as GDBM.
> Here again the data is streamed into a 'QByteArray'. This class is
> used for efficiently indexing a mailbox.
>
> -> I think persistent data must work on any byte-order. The advantage
> of being able to marshal parameters for schemes such as KDE's DCOP, plus
> the advantage of being able to read my mailbox indices on any machine
> are great.
>
> Cheers,
> Rik

Right, but doesn't the issue of what we implement as a default persistence
come into play?

I don't mind if we state here and now that CoreLinux++ framework will
provide both the abstractions and one (1) implementation for persistence as
a minimum. That said implementation will be flat file or stream based. That
said implementation will provide byte ordering protection.

Frank