Re: Using php in custom built http server
| From: | Mr. Gecko | Date: | Sat, 20 Dec 2008 23:28:03 +0000 |
| Subject: | Re: Using php in custom built http server | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-284897@lists.php.net to get a copy of this message | ||
Thanks for the suggestions. I'll read on about it and tell you what I came up with, so if someone else want's to do something similar they can base it off of what I built.
Here are some replies to what you guys asked
I don't know if I would go open source on this.
I can use c code in Objective-C so yeah I can base it off of Lighttpd or Nginx
On Dec 20, 2008, at 2:33 PM, mike wrote:
On Sat, Dec 20, 2008 at 9:37 AM, Nathan Nobbe <quickshiftin@gmail.com> wrote:well now ill have to go scope out nginx :D anyways, major diff between cgi & libphp should be performance, wherein cgi should be like waaay slower. but supposedly fastCGI is pretty solid. peep this thread from a little while back, http://coding.derkeiler.com/Archive/PHP/comp.lang.php/2007-01/msg00120.html and it looks like lighttpd supports fastCGI+php, so again, prob a good source for free working code examples ;Dyou can look at nginx or lighttpd for samples of fastcgi. i think there are some very minor implementation details where one might be better than another, etc. fastcgi is good because it does not tie up the webserver itself with a PHP engine that leaks some memory, but dispatches the request to a separate entity and allows you to scale them separately. a webserver like nginx can do much more work even on a single box - wordpress.com had it pushing 8000 reqs/s of real world load balancing traffic - and then you can focus on giving fastcgi the resources it needs, be it more engines on the same box or splitting it apart and creating a pool of fastcgi engines on N servers... i'd also recommend php-fpm. it makes configuring php for fastcgi elegant, adds in multiple options and will soon adaptively spawn the amount of engines like apache does with webserver threads/processes/whatever as needed...