Error in BSON-reader

Apr 12, 2010 at 9:03 AM


Found this information about an error in the BSON-reader:

"One thing I know is that it has a 
bug in the reader that you'll see if you use a lot of multi-byte unicode 
characters.  It shouldn't happen too often.  It only happens when a 
character is split across the 128 byte buffer it uses to read strings in.

I wonder if this is an issue or if you have solved it?

Have you made any performance measurements between your BSON-writer/reader and Sam Corder's?


Apr 12, 2010 at 11:02 AM

Solved it.

No performance tests. If it uses Json.NET then it would be the same, no?

Apr 13, 2010 at 7:01 PM
Great that the issue is fixed. Sam's driver doesn't make use of your lib, but I do. I that thread there were a hint of that your BSON-implementation was slower. That's why I wondered if you have made any performance measurements between them //Daniel
Apr 15, 2010 at 8:56 AM


I doubt it is still slower but you're welcome to do some benchmarks. I'd be interested in the results.