Object header size limitation about neofs-api HOT 7 CLOSED

taking into account #263, seems like 4K could be enough. If anything, the limit can be raised compatible

or just stock 16K and be sure?

from neofs-api.

Four PATH_MAX seems to be more viable to me, so 16K. At least something that can last.

from neofs-api.

im ok with 16K

from neofs-api.

btw, does the limit apply specifically to header field or to all fields except the payload?

from neofs-api.

I'd think of HEAD reply, but it'd be less convenient to check this way. OID is known to be small, signatures are short as well, the only thing that can be problematic is Header. @carpawell?

from neofs-api.

I think limiting only Header field is OK. Also, if we add more fields here, the same header (the same size) may surprisingly become invalid for the new objects but still be OK for the old ones.

Another question: what about the big objects? Parent header may be OK, but the child parts that have it as a part of their headers may become invalid at the last split step. Do we want to do smth about it?

from neofs-api.

Do we want to do smth about it?

No.

from neofs-api.