Hello all,

In the context of using the C-API and segmented blobs in a generic
context (where the final application writer would not have the choice
of controlling the size of the segments he/she writes to the blob),
what would be a wise guess as to which blob segment size to choose ?

Would you go for simply the largest segments one can write at a time (n
segments of 64K - 1 bytes plus one last segment for the remaining
bytes) ?

Would you go for something just wide enough to fit on a database page ?
But then how to compute the max segment size that would fit on a given
database page size ?

Anything in between ?

I'm adding a high-end blob writer / reader to some interface library to
make it easier for new users to handle blobs when they don't need full
control. Reader is not an issue. Writer forces me to choose for the
users how I will segment the blob while writing it. I'm just trying to
select a decent standard way of slicing the blobs, taken into account
that if the user wants advanced control, this already exists in the
library anyway.

Thanks for ideas and suggestions based on real life experience,

--
Olivier Mascia