ORBit object IDs

Does anyone know why does ORBit insist that object IDs are string-like
and null terminated? AFAIK there's nothing in the standard that requires
that the sequence<octet>s that are object IDs be string-like.

I'm concerned about orbit_poa.c:591, which g_assert()'s null termination,
and also comments elsewhere in the code referring to strlen() of the
object ID - when actually it can be binary data with embedded nulls.

BTW this refers to ORBit 0.5.15, but the same issue may be in ORBit2

Huw Rogers <rogers@building2.co.jp>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]