tree 12d2e38bb1829062bdbb9e84bef08c8a937be233
parent 40c2279e10231cbda0a7ac261e6270f9b223c368
author Ed Tanous <ed.tanous@intel.com> 1528482444 -0700
committer Ed Tanous <ed.tanous@intel.com> 1531157604 -0700

Allow public access to raw message object

There are certain cases where one would like to access the raw message
object under certain contexts.  In general, these are contexts where
you need runtime access to the message type information, rather than
compile time template typing that the existing message object gives
you.  It is still desirable to use the message object itself for
exception safety and RAII usage semantics.

Specifically, this came up when attempting to replicate the actions
interface in phosphor-rest, where types and conversions are determined
at runtime via introspect, and the type hierarchies are not known at
compile time.

Change-Id: I1e93af30992ffedbf470c1024eefe10cc5e21031
Signed-off-by: Ed Tanous <ed.tanous@intel.com>