Hello, To my knowledge it does support external file systems.
The way that I have the webserver running, fsdata.c contains all of my web pages. fsdata.c is in external flash. When http_find_file runs and calls fs_open to find your file you get a file struct with length variables and a pointer to your file which is still sitting in external memory. These variables are then added into the hs struct. Afterwards http_send_data and http_write get called, finally passing your pointer into tcp_write(it is still pointing at external mem at this point). In tcp_write, your webpage from external memory gets copied into pbufs, which exist in ram and the internal lwip stuff sends your data out. I just ran through this in my debugger, so I am pretty sure this is how it works. You should be able to just use the normal fs functions. If anyone sees anything wrong with what I said please point it out. Hope that helps. On Tue, Feb 26, 2013 at 2:16 AM, Philipp Tölke <[email protected]>wrote: > Hello everyone, > > Am 21.02.2013 17:41, schrieb Louis Wells: > > I do not believe that it is necessary to even use fs_custom in this > > situation. > > Is it correct that the httpserver_raw does not support "external" > filesystems and files that do not fit into the RAM? > > Regards, > -- > Philipp Tölke, M.Sc. - Software-Developer - fos4X GmbH - www.fos4x.de > Thalkirchner Str. 210, Geb. 6 - D-81371 München; AG München HRB 189 218 > T +49 89 999 542 58 - F +49 89 999 542 01 > Managing Directors: Dr. Lars Hoffmann, Dr. Mathias Müller > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
