| commit | e288ff90aa151eab4088d109c00aaa348840e215 | |
| author | cdfrey <cdfrey> | |
| Wed, 6 Jun 2007 21:10:25 +0000 (6 21:10 +0000) | ||
| committer | cdfrey <cdfrey> | |
| Wed, 6 Jun 2007 21:10:25 +0000 (6 21:10 +0000) | ||
| tree | 1fbeaa61fd1949328c08a7ae4bc9228128293776 | treesnapshot (tar.gz zip) |
| parent | 4b15e4207c8b97482efd63ba3f462ab6fad1669b | commitdiff |
- did some testing and found that PINMessage's MessageRecordId
is the same as the RecordId given through the SetIds()
API... but these Id's are duplicated in the protocol...
RecordId is stored in the protocol header, while
MessageRecordId is stored in the record it self as
a common field... added RecType and RecordId to
PIN Message so that we store both of these
is the same as the RecordId given through the SetIds()
API... but these Id's are duplicated in the protocol...
RecordId is stored in the protocol header, while
MessageRecordId is stored in the record it self as
a common field... added RecType and RecordId to
PIN Message so that we store both of these
| ChangeLog | diffblobblamehistory | |
| src/r_pin_message.cc | diffblobblamehistory | |
| src/r_pin_message.h | diffblobblamehistory |