Anyone have any guidance on how to handle large HTTP Posts using the Wiz850io?
I currently have code that will handle GET requests for any file off the SD card. One intent of this project is to allow editing of the configuration INI file on the SD card through the web interface, and save it back to the card (backing up the original)
I now need to post back the contents of the editor page. While I have no doubt I can do it, I would appreciate any high-level hints for the best method for handling the large amount of data. And when I say large, lets say (hopefully) under 20kb
I could create a fixed size buffer...but I'd need one for each socket which would largely go unused and suck up most of my memory.
I could manually malloc a buffer which seems the better way, based on the content-size header.
I know there are ramifications of each when it comes to memory allocation though I'm not smart enough to understand the inner workings of the heap and stack.
At what point do I have to worry about filling up the buffers in the network library and/or the wiz? (I'm also using the audio board and ethernetAudio so I'm conscious of making sure I don't hang the code up for too long. )
I see the Wiz has a 32kb for send/recv. One could only hope/assume that if it fills up it's buffers, that it will slow the TCP ACKs down?
Thanks!
I currently have code that will handle GET requests for any file off the SD card. One intent of this project is to allow editing of the configuration INI file on the SD card through the web interface, and save it back to the card (backing up the original)
I now need to post back the contents of the editor page. While I have no doubt I can do it, I would appreciate any high-level hints for the best method for handling the large amount of data. And when I say large, lets say (hopefully) under 20kb
I could create a fixed size buffer...but I'd need one for each socket which would largely go unused and suck up most of my memory.
I could manually malloc a buffer which seems the better way, based on the content-size header.
I know there are ramifications of each when it comes to memory allocation though I'm not smart enough to understand the inner workings of the heap and stack.
At what point do I have to worry about filling up the buffers in the network library and/or the wiz? (I'm also using the audio board and ethernetAudio so I'm conscious of making sure I don't hang the code up for too long. )
I see the Wiz has a 32kb for send/recv. One could only hope/assume that if it fills up it's buffers, that it will slow the TCP ACKs down?
Thanks!