3 ms·
I've read the introduction and I still don't quite know what the fuss is all about. Perhaps some examples of its benefits right in the introduction?
by arturadib 16y ago
I've read the introduction and I still don't quite know what the fuss is all about.
Perhaps some examples of its benefits right in the introduction?
- steveklabnik 16y agoFirst of all, there's a fuss because it's written by zedshaw. Secondly, zedshaw also authored mongrel, a well-known web server that many people have taken the ragel-based parser from to build their own stuff. Third, everyone's been talking about this whole 'sqlite as configuration' thing, which could be awesome or horrible, the jury's still out. Finally, it's always interesting to see new projects in 'solved' areas. How long has Apache been around? How well is it tested? It obviously works, but could it be better? Zed's trying out new ideas, has a crazy amount of test coverage, and is starting out fresh. I haven't tried it yet. But it's certainly interesting.
- jshen 16y agowhat your'e saying is that there isn't yet a compelling reason for most people to try it.
- mikeryan 16y agoSounds like there are a ton of compelling reasons to try it.
- jshen 16y agoAs someone who runs multiple sites and who doesn't have a major problem with apache, what here should compel me to try it? Ragel parser? Um, why should I care if I'm not going to dig into the code myself? because zedshaw is so fucking awesome? Not a compelling reason to try a web server to me, is it to you? sqlite configuration? Maybe, but that's not super compelling to me at the moment. despite my sarcasm, my question is sincere. I'm curious how mongrel2 could be an improvement over what is currently used, which for me is mostly apache Any other reasons?
- zedshaw 16y agoI'm a firm believer that if it ain't broke don't fix it. If you've got multiple sites working with Apache and you know how to keep that going smooth, then stick with that. Especially if you're doing small to medium sites in say PHP. PHP and Apache are kind of the king and queen of the realm. What Mongrel2 has over Apache is it's ability to run async jssockets, HTTP long poll style work, and regular HTTP at the same time. If you hit an application where you want to do some async socket type stuff, that's when you should look at Mongrel2. Of course, that's not all it does, but if you already love your Apache and it's crazy config file format and weirdo 1995 style syntax, then Mongrel2's only addition is the extra protocols.
- jshen 16y agothanks, that makes perfect sense. No, I don't love apache's crazy config file format, but I don't update the config often and it's mostly copy and paste when I need to add something new. It's rails with passenger which is pretty easy. I'll definitely check out the async stuff, that is compelling!
- alexgartrell 16y agoThe name of the game is flexibility. Configure your web server in any language you want (so long as it has sqlite bindings). Serve your web pages from any back-end you want (so long as it has zeromq). Has it turns out, zeromq and sqlite are low barriers to entry for any language. You're right though, in that you can do all of this with apache, if you're willing to write the right config generator and install (or create) mod_*. Mongrel2 just makes it easy. edit: Also, what zed said :)
- zedshaw 16y agoHmm, I'll think about that one too. Truth is, I just built it, so kind of a cobbler's shoes problem in that I've had little time to actually use it other than to run mongrel2.org with it. So far the people who are playing with it talk about how easy it is to work with and deploy one of the 10 programming language platforms using ZeroMQ.