Thanks for reminding me I had a recurring payment set up to go to these guys... Cancelled. Their cancellation process is a royal PITA as well (there's a surprise).
I never could get anything working under Cedega without major pain, not worth it.
Just because there's some arbitrary technical reason for their current process doesn't mean they shouldn't change it if they don't want it to happen again.
If its publically accessible its fair game, they have only themselves to blame.
Yep, very impressed by how clean and usable it was. No special software required, no Java/ActiveX needed, and a fast efficient workflow. Took a few minutes and I was done.
Err. Has the reviewer in question seen the Cinema line from Apple? No? Okay.
Because this Asus is not even playing the same game with regards to design. My 2 year old Dell 2001FP looks better. Oooh shiny brushed metal base. Pity about the rest of the monitor though.
Huge black borders with speakers for the wtfpwned, bbq'd, loss. If I wanted sound, I'd get 5.1, not 0.0 on my monitor.
Now this is where I have to agree. mod_rewrite is without question, Apache's killer module.
You can fake something with IIS+ASP.NET and an IHttpModule, or by writing an ISAPI module (basically, reimplementing mod_rewrite for IIS), but its not the real deal.
No thanks.
I don't want a Perl interpreter mucking around in my web server's internals. I prefer the FastCGI approach, where applications stay the hell out of the web server's address space.
Not too sure what this has to do with Apache configuration. Putting the code inside the configuration file itself isn't exactly the solution I'm looking for, more like being able to modify the config from outside of it using scripts.
Yeah, includes are about the only way to do it sanely.
Along with "graceful", this gives some measure of managability...The important part being that all the configs are generated by scripts and not hand-edited.
Okay...So I guess the OP fixated on one thing (modular configuration snippets) and wrote off all IIS efforts as copying.
It is this complacent attitude that will get Apache's ass handed to it.
When I last checked, Apache has no way (short of parsing the config file with your own crappy scripts using unreliable regexen ) for you to inspect the current configuration. IIS has this, the entire object model of the server configuration is available for inspection from the scripts, guaranteed to be accurate.
Apache needs to provide (if not a more structured file format), a set of script-callable APIs for configuring and managing the server.
Grepping the config file and making one or two changes then restarting may be sufficient when you're running 10 or 20 sites in production, but when you're hosting 1000s, you need something better.
IIS is also completely manageable from scripts, and I cast envious glances at the things our IIS admins are able to do with scripts. Create new vhost: Check. Temporarily disable vhost: Check. Modify vhost properties at runtime without bouncing the entire server: Check.
Apache doesn't have anything equivalent (unless you count the big-hammer apachectl START/STOP/GRACEFUL) as "management". Or you write your own. (Yeah, we all have time to reinvent that wheel.)
Apache is playing catch up here in every sense.
And this comes from someone who runs tonnes of sites under Apache in production.
Believe me, generating Apache configuration from a canonical source (i.e. a database) is a royal pain in the ass, but currently the only way you're really going to manage 1000s of sites with Apache if you're offering hosting services.
This management is the single biggest thing missing in Apache today.
how tired is the blue screen of death??
on
Moving To Linux
·
· Score: 1
um, yeah, so i've had windows XP crash exactly 0 times in 3 years. the blue screen of death is so yesterday!
Slashdot Mirror
To quote South Park: Novell just got F'd in the A.
Microsoft launches a new developer community website every few months. I'm confused as to which one is the real one. Someone please inform?
..the fuck?
Thanks for reminding me I had a recurring payment set up to go to these guys... Cancelled. Their cancellation process is a royal PITA as well (there's a surprise).
I never could get anything working under Cedega without major pain, not worth it.
Just because there's some arbitrary technical reason for their current process doesn't mean they shouldn't change it if they don't want it to happen again.
If its publically accessible its fair game, they have only themselves to blame.
Yep, very impressed by how clean and usable it was. No special software required, no Java/ActiveX needed, and a fast efficient workflow. Took a few minutes and I was done.
IronPort works extremely well too. Be prepared to pay enterprise prices though.
Err. Has the reviewer in question seen the Cinema line from Apple? No? Okay.
Because this Asus is not even playing the same game with regards to design. My 2 year old Dell 2001FP looks better. Oooh shiny brushed metal base. Pity about the rest of the monitor though.
Huge black borders with speakers for the wtfpwned, bbq'd, loss. If I wanted sound, I'd get 5.1, not 0.0 on my monitor.
Now this is where I have to agree. mod_rewrite is without question, Apache's killer module.
You can fake something with IIS+ASP.NET and an IHttpModule, or by writing an ISAPI module (basically, reimplementing mod_rewrite for IIS), but its not the real deal.
No thanks. I don't want a Perl interpreter mucking around in my web server's internals. I prefer the FastCGI approach, where applications stay the hell out of the web server's address space. Not too sure what this has to do with Apache configuration. Putting the code inside the configuration file itself isn't exactly the solution I'm looking for, more like being able to modify the config from outside of it using scripts.
Yeah, includes are about the only way to do it sanely.
Along with "graceful", this gives some measure of managability...The important part being that all the configs are generated by scripts and not hand-edited.
Okay...So I guess the OP fixated on one thing (modular configuration snippets) and wrote off all IIS efforts as copying.
It is this complacent attitude that will get Apache's ass handed to it.
When I last checked, Apache has no way (short of parsing the config file with your own crappy scripts using unreliable regexen ) for you to inspect the current configuration. IIS has this, the entire object model of the server configuration is available for inspection from the scripts, guaranteed to be accurate.
Apache needs to provide (if not a more structured file format), a set of script-callable APIs for configuring and managing the server.
Grepping the config file and making one or two changes then restarting may be sufficient when you're running 10 or 20 sites in production, but when you're hosting 1000s, you need something better.
IIS is also completely manageable from scripts, and I cast envious glances at the things our IIS admins are able to do with scripts. Create new vhost: Check. Temporarily disable vhost: Check. Modify vhost properties at runtime without bouncing the entire server: Check.
Apache doesn't have anything equivalent (unless you count the big-hammer apachectl START/STOP/GRACEFUL) as "management". Or you write your own. (Yeah, we all have time to reinvent that wheel.)
Apache is playing catch up here in every sense.
And this comes from someone who runs tonnes of sites under Apache in production.
Believe me, generating Apache configuration from a canonical source (i.e. a database) is a royal pain in the ass, but currently the only way you're really going to manage 1000s of sites with Apache if you're offering hosting services.
This management is the single biggest thing missing in Apache today.
um, yeah, so i've had windows XP crash exactly 0 times in 3 years. the blue screen of death is so yesterday!
cool, you read slashdot too? glad my backup DNS server is hosted at rimu :)