Re: Chunking throwing IOException

On 06/16/2013 07:33 PM, Justin T. Sampson wrote:
> hOn the other hand, I would question the idea of ignoring stream 
> corruption. If a chunk was /incompletely/ written, Chunking.readChunk 
> throws an EOFException, which /will/ be ignored. The exception you're 
> actually seeing indicates that data /was/ written, but was somehow 
> corrupted rather than merely truncated.

Yeah, I think a decision to just drop corrupted transactions in the 
middle would have to be on a per-project basis. I've worked on some 
projects where I'd want the system to come up and chug along (but warn 
me) and others where it would absolutely have to stay down until the 
problem was manually resolved. E.g., in a financial trading system, no 
trading is better than making trades based on an incorrect understanding 
of the position.

William

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org