5 ms·

Decent idea, except for the part where you made it an Apache module. If you'd instead built an app/middleware/server spec like Python's WSGI or Ruby's Rack, it'

Decent idea, except for the part where you made it an Apache module. If you'd instead built an app/middleware/server spec like Python's WSGI or Ruby's Rack, it'd be possible to use this sort of thing with more lightweight servers.

randallsquared 18y ago
It appears he traded some immediate use for greater ultimate potential, if believe that much of PHP's success is due to optimizing for ease of use with Apache first. (After actually reading TFA, I realize that he actually did it as mod_v8 because he's an Apache maintainer or something).
davidw 18y ago
Paul Querna is one of the Apache httpd developers, so I think he's quite likely to go on using Apache, instead of the event based server du jour.
- inklesspen 18y ago
  Well, that's nice for him, but not so nice for us.
  - EliAndrewC 18y ago
    If he does decide to pursue this project, probably the most important thing that will affect whether it gets completed is how useful it is to him and how much fun he has while doing it. I'd definitely love to see a more generic system that's not tied to Apache, but I'm fine with him starting off with an Apache specific setup if that's what gets him motivated and interested.
    - davidw 18y ago
      Right - that's how open source works. Scratch your own itch, and work on things you like. If someone wants to see something not based on Apache, well, you have the source code, a compiler, and an editor. Also, Apache is a perfectly fine web server. These event-based things have been around for a while. I recall moving the images and some other static assets on linuxcare.com to the Boa web server to save memory. However, Apache manages to have its own advantages, and stay relevant through the hard work of people like Paul Querna, even if, no, it's probably not the absolute fastest/smallest thing out there. Look at Rails - after going through a succession of various mixes of lighttpd, nginx, mongrel, etc.. etc... it's now coming back around to Apache and Passenger, and rightly so, Passenger is a nicer, simpler, more robust way of doing things. Furthermore, in terms of the other post's "him" and "us", there are a lot more of "him" (Apache users) than "us" (users of whatever other system).

randallsquared 18y ago

It appears he traded some immediate use for greater ultimate potential, if believe that much of PHP's success is due to optimizing for ease of use with Apache first. (After actually reading TFA, I realize that he actually did it as mod_v8 because he's an Apache maintainer or something).

davidw 18y ago

Paul Querna is one of the Apache httpd developers, so I think he's quite likely to go on using Apache, instead of the event based server du jour.

inklesspen 18y ago
Well, that's nice for him, but not so nice for us.
- EliAndrewC 18y ago
  If he does decide to pursue this project, probably the most important thing that will affect whether it gets completed is how useful it is to him and how much fun he has while doing it. I'd definitely love to see a more generic system that's not tied to Apache, but I'm fine with him starting off with an Apache specific setup if that's what gets him motivated and interested.
  - davidw 18y ago
    Right - that's how open source works. Scratch your own itch, and work on things you like. If someone wants to see something not based on Apache, well, you have the source code, a compiler, and an editor. Also, Apache is a perfectly fine web server. These event-based things have been around for a while. I recall moving the images and some other static assets on linuxcare.com to the Boa web server to save memory. However, Apache manages to have its own advantages, and stay relevant through the hard work of people like Paul Querna, even if, no, it's probably not the absolute fastest/smallest thing out there. Look at Rails - after going through a succession of various mixes of lighttpd, nginx, mongrel, etc.. etc... it's now coming back around to Apache and Passenger, and rightly so, Passenger is a nicer, simpler, more robust way of doing things. Furthermore, in terms of the other post's "him" and "us", there are a lot more of "him" (Apache users) than "us" (users of whatever other system).