Le 11-12-06 13:26, Milan Crha a écrit :
Hi,
maybe a newbie question, but I never understood why there is SPropValue
and mapi_SPropValue, or at least those unions for values. I didn't think
of it much till now, as it seems to me that mapi_SPropValue(_CTR) is
just an overhead, as the inner unions (those _CTR) should be identical
between these two structures and having everything in defined twice is
sometimes confusing.
Can anyone correct me and tell me what the reason was, please?
Thanks in advance and bye,
Hi Milan,
Those structures correspond to different representations of the same
datatypes, depending on where they are rendered or parsed in the protocol.
For example, a PT_BINARY property will always be rendered as a
mapi_SPropValue when transferred via a RopGetProperties or a
RopQueryRows but as a SPropValue when transferred via the stream ROPs or
the FastTransfer ROPs.
Basically, the mapi_ ones are made to not take more than 32767 bytes
while the non-mapi ones can be 2^32-1 bytes long, this does not apply to
small values but will apply to string, binary and array values...
Cheers,
Wolfgang
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
