ver; (b) it is varible in size, and
therefore, does not lend itself to smart and effective parsing; (c) the
searching based on the complete POA name is very ineffient.</li>

<p>The new solution is to use an active demux table, and flatten the POA
hierarchy. This will help in the searching since active demuxing is fast
and predictable. This will also help in the parsing since the demux key
will be fixed size.
<p>Note that for persistent ids, we have to pass the complete POA name
in addition to the demux key 