[lwip-devel] [bug #20506] HTTP server doesn't call tcp_output

[Frédéric Bernon]

Follow-up Comment #9, bug #20506 (project lwip):

>But in the contrib module, there are 2 httpd.c servers (in
contrib/ports/msvc6 and contrib/ports/unix/proj/unisxsim/apps), and they have
the same problem (those are RAW api servers). It looks like they are exactly
the same as the example httpd in vipin's zip file. 

To my point of view, it should be better to move such samples from "ports" to
"contrib/apps". Of course, there is a problem with the initialization part
which can be specific, but most of the code is "independant" of any ports
(except the "leds" called in httpd.c). Perhaps we could propose a kind of
"framework" for sample, where each sample have to implement a
lwip_sample_main() function, and each sample_port have to call it ?

>That would probably change something but it's not the cause of the problem!


Yes, it was the "enough" side :)

>It is rather mandatory to call tcp_output (tcp_output_nagle is not available
in v1.2.0) after having called tcp_write!

That's why I provide the define at the end of comment#6 :). Note the
tcp_output is really not "mandatory" since it work without but it's not
efficient (so saying "strongly recommanded" :) .

Vipin, can you confirm us if one of these solutions work for you ?


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?20506>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/