MONGOC_CLIENT_...X_MESSAGE_SIZE(3)

💖 MONGOC_CLIENT_...X_MESSAGE_SIZE(3) 💖

okay bestie, welcome to the libmongoc corner of the manual, this one's short and sweet and also kinda retired, so let's get into it 🎀

---

✨ NAME ✨

mongoc_client_get_max_message_size — the lil function that tells you how big a message the cluster will let you send 🦋

---

✨ SYNOPSIS ✨

int32_t
mongoc_client_get_max_message_size (mongoc_client_t *client);

so like, mongoc_client_get_max_message_size() hands you the maximum message size that the cluster allows, no cap. but here's the tea: until a connection has actually been made, it just gives you the default of 40Mb. it's giving "i don't know yet so here's a guess" energy 🙈

---

💀 DEPRECATED 💀

WARNING: this function is deprecated and should not be used in new code. like, she's retired, she's living her best life, do not put her back to work. periodt. 💅

---

✨ PARAMETERS ✨

• client: a mongoc_client_t. that's it. that's the whole list. one (1) single parameter. iconic honestly 👑

---

✨ RETURNS ✨

the max message size that the server provided 🫶 — or 40Mb if no connection has been established yet. so if you're getting 40Mb back, that might be a real answer or it might just be the "we haven't talked to anybody yet" default, iykyk 😭

---

✨ AUTHOR ✨

MongoDB, Inc — the icons who made this whole thing ⭐

---

✨ COPYRIGHT ✨

2017-present, MongoDB, Inc 🍓

---

okay that's the whole page, you ate that, go forth and don't use the deprecated function bestie 💜

libmongoc, version 1.23.1, dated Apr 27 — mwah, love u, bye 🎀✨💖