[lwip-users] httpserver with http1.1 header

Hi, I'm using raw lwip1.4 with http server from contrib-1.4.0. Http headers are generated dynamically. The server uses SSI. I figured out that the server generates http1.0 headers by default. I want to generate http1.1 headers. My main problem is the size of the Content-Length, specially the size o

Re: [lwip-users] using lwIP in commercial product

Hi, We are using lwip on our project. Lwip is use as a client for audio streaming and at the same time as a webserver. On the beginning of our project we encountered some difficuties by now the problems are fixed. Let say the first steps are not easy but on the other hand lwip is too powerful to

[lwip-users] problem closing a stream

Hi, I'm using lwip 1.3.2 in an audio stream client application. I close my application like this: static void httpclient_connection_close(struct tcp_pcb *tpcb, struct httpclient * hc ) { if (hc->pcb) { tcp_arg(hc->pcb, NULL); tcp_sent(hc->pcb, NULL);

Re: [lwip-users] flow of lwip as a stream client

Again thanks for the helpful suggestions. I change the algorithm in a way that when the private buffer can accomodate more than TCP_WND I call the tcp_recved() with TCP_WND otherwise I call tcp_recved() with remaining buffer size. I need to review my code though because the tcp received callback

Re: [lwip-users] flow of lwip as a stream client

ecved(). What should I do will the pbuf? Or do you think the tcp receive callback is not called at all? Trex goldsi...@gmx.de wrote: > > trex7 wrote: >> -I dont realy understand what you mean. I think, the scenario that I >> cannot >> process the incomming pb

Re: [lwip-users] flow of lwip as a stream client

data. Please correct me if I misunderstood anything. Thanks for you patience. Trex goldsi...@gmx.de wrote: > > trex7 wrote: >> I tried different cases when the buffer is full and I cannot process the >> incomming pbufs >> 1. I just ignore them, no pbuf_free(). AND of

Re: [lwip-users] flow of lwip as a stream client

>>I think that you should buffer the pbufs, and NOT call tcp_recved() >> until you consume a pbuf in your audio task. Nice Idea but thats one of the purpose of the buffer, to buffer the stream so we can call tcp_recved as soon as possible so lwip can advertise a larger window. Trex -- Stephan

Re: [lwip-users] flow of lwip as a stream client

Thank you for answers. I tried different cases when the buffer is full and I cannot process the incomming pbufs 1. I just ignore them, no pbuf_free(). AND of course no tcp_recved(). 2. I free the pbuf with pbuf_free(). As always no calling of tcp_recved(). 3. I returned ERR_INPROGRESS and no pbuf_

Re: [lwip-users] flow of lwip as a stream client

> counter = (counter+1) % bufferSize > > I hope this can help you. > > Regards > Robert > > Am 01.03.2012 16:09, schrieb trex7: >> Hi, >> I'm using raw lwip 1.3.2 as a client for an audio stream based >> application. >> I'm a bit confuse how

[lwip-users] flow of lwip as a stream client

Hi, I'm using raw lwip 1.3.2 as a client for an audio stream based application. I'm a bit confuse how to handle the incomming pbufs when the audio buffer is full and I have to wait until the audio buffer has enough space to accomodate the pbuf. My code looks something like this: errt_t http_recv_