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 implementation of at45db, where bad data on > > a page and end of log conditions are generally synonymous. > > I'm simply envisioning that it's guaranteed (well, within the bounds > provided by simple error detection codes) not to return invalid data. > It's actual behaviour on invalid data would be left unspecified (skip, > think it's end of log, whatever - we might want to guarantee that it > does return at least, though).
Yeah, I asked an impl ? in a spec context. Sorry about that. What you are suggesting should would work well for our expected uses of log storage. A thought: You earlier introduced the idea of having appendDone deliver indication of data lost due to a circular log wrap. A similar change to readDone could deliver indication of data lost to corruption. Thanks, Steve _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
