CORBA34 — Custom Value Marshaling Issue

Due to the way that custom values are marshaled it is
nearly impossible for a bridge (or other process) to
process/forward GIOP messages which contain custom
marshaled values (which the bridge has no compile/run-time
knowledge of).

The main issue is that the "alignment" of the
custom marshaled data is unknown, other than the
data will always start on a four byte boundry due
to the presence of chunking.

Should/could the value encoding format be changed to
enforce eight byte alignment for all custom marshaled
data (chunks)? This would allow bridges and other
tools to process->[store]->forward messages containing
custom values.

Deferred

This proposal was generated automatically by request of the Task Force Chair Adam Mitz.