{"push_id":2464397319,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"dc724c140d23158ac3059292b27962cc276acdc8","before":"3cb7a5c672d9f817a498684ac7057bcccc713eda","commits":[{"sha":"dc724c140d23158ac3059292b27962cc276acdc8","author":{"name":"Alan Conway","email":"f52ac7f18aee66f8da492e36fb0a920cfff785a4@redhat.com"},"message":"PROTON-1823: [c] pn_message_send() simplified message sending for C\n\nEncapsulates the awkward allocate-encode-expand dance required by pn_message_encode()\nSupports the following 2 scenarios:\n\n1. Simple: don't care about allocations, just send `pn_message_t *msg` and forget it:\n\n    pn_message_send(msg, sender, NULL)\n\n2. Efficient: re-use a buffer, buffer is allocated and expanded as required:\n\n    pn_rwbytes_t buffer={0};     // Zero initialize, libary will do the allocation\n    ...\n    pn_message_send(msg, sender, &buffer); // Expand as needed\n    pn_message_send(msg2, sender2, &buffer); // etc.\n    ...\n    free(buffer->start);        // Application must do final free of buffer\n\nNote 2. assumes use of malloc/realloc/free, apps that need custom allocation can\nuse the original pn_message_encode() API or we could add a version that takes a pointer\nto a function equivalent to realloc()\n\nUpdated examples to use this API.","distinct":true,"url":"https://api.github.com/repos/apache/qpid-proton/commits/dc724c140d23158ac3059292b27962cc276acdc8"}]}
{"actor":{"display_login":"asfgit"}}