Hey there, in the current implementation the STUN_CLIENT_DATA struct is more than 130k, having statically allocated a whole bunch of things. This makes it fairly hard to use in embedded scenarios, where that much isn't available. The main culprit is STUN_TRANSACTION_DATA of which there is 60 x 2200b allocated. I'm planning on working to shrink down this memory usage, firstly by being able to define your own MAX_STUN_TRANSACTIONS, however would like to take it down to something sub-5k. Any tips/ideas how you would go about doing so? There's a bunch of statically allocated strings (i.e. stun username) that could be smaller if they aren't needed (i.e. using a public STUN server).
Hey there, in the current implementation the STUN_CLIENT_DATA struct is more than 130k, having statically allocated a whole bunch of things. This makes it fairly hard to use in embedded scenarios, where that much isn't available. The main culprit is STUN_TRANSACTION_DATA of which there is 60 x 2200b allocated. I'm planning on working to shrink down this memory usage, firstly by being able to define your own MAX_STUN_TRANSACTIONS, however would like to take it down to something sub-5k. Any tips/ideas how you would go about doing so? There's a bunch of statically allocated strings (i.e. stun username) that could be smaller if they aren't needed (i.e. using a public STUN server).