On Tue, Feb 4, 2014 at 3:35 PM, Fraser Adams <[email protected]>wrote:
> So this happens in message.c in > int pn_message_encode(pn_message_t *msg, char *bytes, size_t *size) > > ...... > > err = pn_data_fill(msg->data, "DL[CzSSSCssttSIS]", PROPERTIES, > msg->id, > pn_string_get_bytes(msg->user_id), > pn_string_get(msg->address), > pn_string_get(msg->subject), > pn_string_get(msg->reply_to), > msg->correlation_id, > pn_string_get(msg->content_type), > pn_string_get(msg->content_encoding), > msg->expiry_time, > msg->creation_time, > pn_string_get(msg->group_id), > msg->group_sequence, > pn_string_get(msg->reply_to_group_id)); > > > so basically it looks like it populates *all* standard PROPERTIES even if > they aren't *explicitly* set. > > I commented that based on what I was seeing it looked like qpid::messaging > wasn't using Proton's message code 'cause qpid::messaging only seems to be > sending properties that have been explicitly set. > > > > It's probably worth aiming for consistency, but TBH I'm an awful lot more > concerned that Proton Messenger doesn't seem to have a mechanism for > setting link configuration and thus I couldn't use it for most of my more > interesting examples, which was a shame. > > Nobody has yet confirmed nor refuted whether this observation is correct. > I'd like to know for sure and if that stuff isn't supported I'd love to > know what the intentions are. > I can confirm your observations are correct. As for intentions, I would certainly like to support link configuration, the only reason it hasn't happened yet is due to me being pulled in too many directions at once. --Rafael
