The first thing I would do would be to use Wireshark to see what exactly the timing on the network is.It was a bug in thttpd – it wasn't accounting for the length of the headers properly. I'll make a PR for it once I get a few other issues worked out. The thttpd performance is a lot worse then uIP webserver– this shouldn't be the case. Maybe there is a resource bottleneck of some kind. I tried adjusting some of the config settings for sockets/file descriptors/etc. but haven't had any luck. I might have to profile the app.
- thttpd question Adam Feuer
- Re: thttpd question (TCP close problem?) Adam Feuer
- Re: thttpd question (TCP close problem?) Xiang Xiao
- Re: thttpd question (TCP close problem?) Adam Feuer
- Re: thttpd question (TCP close problem?) Adam Feuer
- Re: thttpd question (TCP close problem?... Adam Feuer
- Re: thttpd question (TCP close prob... Adam Feuer
- Re: thttpd question (TCP close ... Gregory Nutt
- Re: thttpd question (TCP close ... Adam Feuer
- Re: thttpd question (TCP close ... Gregory Nutt
- Re: thttpd question (TCP close ... Adam Feuer
- Re: thttpd question (TCP close ... Gregory Nutt
- Re: thttpd question (TCP close ... Adam Feuer
- Re: thttpd question (TCP close ... Gregory Nutt
- Re: thttpd question (TCP close ... Adam Feuer