X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=src%2Frmr%2Fnng%2Fsrc%2Frmr_nng.c;h=720f6ade6ce722b89eb50978c06fda174e59dba4;hb=ec88d3c0563eeb6ae5f73427edb0b3c4d7acf299;hp=d9c4c061c3759cea494b3d3260bcb2df642461c1;hpb=7d1b7b0de82414ad25ebd323b2913de72ab448c1;p=ric-plt%2Flib%2Frmr.git

diff --git a/src/rmr/nng/src/rmr_nng.c b/src/rmr/nng/src/rmr_nng.c
index d9c4c06..720f6ad 100644
--- a/src/rmr/nng/src/rmr_nng.c
+++ b/src/rmr/nng/src/rmr_nng.c
@@ -1086,3 +1086,40 @@ extern rmr_mbuf_t* rmr_mt_call( void* vctx, rmr_mbuf_t* mbuf, int call_id, int m
 
 	return mbuf;
 }
+
+/*
+	Given an existing message buffer, reallocate the payload portion to
+	be at least new_len bytes.  The message header will remain such that
+	the caller may use the rmr_rts_msg() function to return a payload
+	to the sender. 
+
+	The mbuf passed in may or may not be reallocated and the caller must
+	use the returned pointer and should NOT assume that it can use the 
+	pointer passed in with the exceptions based on the clone flag.
+
+	If the clone flag is set, then a duplicated message, with larger payload
+	size, is allocated and returned.  The old_msg pointer in this situation is
+	still valid and must be explicitly freed by the application. If the clone 
+	message is not set (0), then any memory management of the old message is
+	handled by the function.
+
+	If the copy flag is set, the contents of the old message's payload is 
+	copied to the reallocated payload.  If the flag is not set, then the 
+	contents of the payload is undetermined.
+*/
+extern rmr_mbuf_t* rmr_realloc_payload( rmr_mbuf_t* old_msg, int new_len, int copy, int clone ) {
+	if( old_msg == NULL ) {
+		return NULL;
+	}
+
+	return realloc_payload( old_msg, new_len, copy, clone );	// message allocation is transport specific, so this is a passthrough
+}
+
+/*
+	The following functions are "dummies" as NNG has no concept of supporting
+	them, but are needed to resolve calls at link time.
+*/
+
+extern void rmr_set_fack( void* p ) {
+	return;
+}