On Tuesday 29 August 2006 10:05 am, David Gay wrote:
On 8/28/06, R. Steve McKown [EMAIL PROTECTED] wrote:
I'd love to see the spec guarantee that read returns valid data. Are you
envisioning a read returns a len of 0 on bad data or end of log? This
seems to fit nicely with the
On 8/28/06, R. Steve McKown [EMAIL PROTECTED] wrote:
So shouldn't then TEP 103 specify data integrity requirements? I can't
imagine a use of log storage where it'd be ok to read back different data
than I'd originally appended. And if that's true, wouldn't data integrity be
more efficient
On Monday 28 August 2006 16:53, David Gay wrote:
On 8/28/06, R. Steve McKown [EMAIL PROTECTED] wrote:
So shouldn't then TEP 103 specify data integrity requirements? [snip]
[snip]
A reasonable compromise might be that read is guaranteed to return
valid data.
I'd love to see the spec
On 8/25/06, R. Steve McKown [EMAIL PROTECTED] wrote:
Hi,
It seems the only method supported by TEP 103 to determine an empty LogStorage
log is to perform a read and receive 0 bytes in return. Is this a correct
assessment?
Hmm, yes.
I can't find where TEP 103 specifies the initial read
On Friday 25 August 2006 09:59 am, David Gay wrote:
On 8/25/06, R. Steve McKown [EMAIL PROTECTED] wrote:
What's the best practice for initially configuring the various
Block/Log/Config storage components' volumes, especially in a moderate
volume production setting? I'm currently thinking a
On 8/25/06, R. Steve McKown [EMAIL PROTECTED] wrote:
I'm thinking more about initializing flash volumes for the various storage
abstractions. Initialization would be an issue for new motes with factory
fresh flash, or motes which have been reprogrammed after a change to the
volume organization
