From: rajyalakshmi bommaraju <rajyalakshmi.bommaraju@intel.com>
To: ofono@ofono.org
Subject: File Structure for persisting history in a disk file (Comments please)
Date: Mon, 01 Nov 2010 12:06:59 -0700 [thread overview]
Message-ID: <4CCF0FD3.9050705@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Hello,
I want to use the following file structure for persisting history in a
disk file. Can you please send me your feedback about it.
Thanks
Raji Bommaraju
_File structure for History
Persistance_
History information will be stored in a disk file. The file will have a
File Header consisting of "Bytes Stored" and "Head" for writing the next
record.Each record stored will have record header and record data,
record header has "record type" and "size of the record" (For Text
messages the records will have variable length message data resulting in
variable length records) hence this record structure is used.
*File Format:*
|File Header| Data |
File Header (8 bytes):
|Bytes stored | Head|
0 4 8
*Data:*
|Record|Record|.....etc
*Record:*
|Record Header|Actual data|
*Record Header:*
Record Type: 1byte (voice call history - 0, text history- 1)
Size : Integer
Actual data: Will be voice call or text message information
reply other threads:[~2010-11-01 19:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CCF0FD3.9050705@intel.com \
--to=rajyalakshmi.bommaraju@intel.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox