RE: [lwip-users] (no subject)

[John Horton]

Thanks Kieran, I will take a look at lighttpd.

I guess I should have been more specific.
I did mean preferably one that had been ported to lwIP, but no need for
this as I want to design my own anyway.

I am using the raw API because a nice simple s/w i/f is what I need for
the intended embedded target. I don't see the need to use another layer
of socket buffering when we only have limited RAM/ROM/processing
resources.

FYI, until our h/w is ready, I have ported lwIP to Win32 (DevCPP +
mingw) using the latest winpcap as the network driver such that I can
bypass the Microsoft stack to test lwIP with our own SNMP, telnet, HTTP
etc on top.

Thanks again for the help and a superb stack.

John


> -----Original Message-----
> From: Kieran Mansley [mailto:address@hidden
> Sent: 31 August 2006 10:52
> To: Mailing list for lwIP users
> Subject: Re: [lwip-users] (no subject)
> 
> On Thu, 2006-08-31 at 10:41 +0100, John Horton wrote:
> > Before I embark on implementing a HTTP server from scratch for LWIP,
> > does anybody know of a free one with source code that I could refer
> > to?
> 
> There are lots of free web servers with source code.  Do you mean one
> that has been ported to use the lwIP raw API?  If using the sockets
API,
> porting the server should just be (at best) a matter of recompiling
it.
> If the shared library we have in the contrib tree were in better shape
> you probably wouldn't even need to do that as it could just be
> "LD_PRELOAD"ed to intercept the socket calls.
> 
> If I was starting this I'd choose a simple, small webserver like
> lighttpd as a basis.
> 
> Kieran
> 
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users


Disclaimer:
This message is intended for the use of the individual(s) or entity named 
above. It may contain information which is privileged or confidential.
If you are not the intended recipient, please return it to sender as soon as 
possible and be aware that any disclosure, copying, distribution or use of its 
contents is prohibited. The views expressed in this communication may not 
necessarily be the views held by the company.