Microsoft IIS v7 Details Emerge
daria42 writes "According to several .NET and Longhorn bloggers, the next version of Microsoft's IIS web server will integrate ASP.NET and turn many core features into optional modules in order to provide a smaller security footprint for hackers to attack. In addition, the software's admin tool has been completely revamped, and will allow Web-based remote administration utilising SSL."
This is what apache did with modules ages ago and webmin did years ago aswell. Although all of it seems to be good what MS is doing, it is late with a few years again.
It takes a man to suffer ignorance and smile
Be yourself no matter what they say
I don't know I think they should improve the multimedia console one. Webbased admin tool might just end up full of holes anyways.
I also noticed the upcoming virtual server 2005 SP1 is using a webbased admin tool. Why something like a virtual machine needs IIS to run to mangage is a little baffling but there seems to be someone at microsoft who always comes up with these terrible ideas.
did you forget to take your meds?
I know it is against "not invented here", but why don't they take a decent BSD-licensed web-server, and then "embrace and extend" the thing to do their proprietary extensions?
If they've modularized their stuff, this should be possible. They've done this already with TCP/IP, Kerberos and so on.
The overall product, to the extent that it benefitted from the work of free BSD-licensed improvements, would be good for everybody.
http://www.thebricktestament.com/the_law/when_to_
Are they going to fix their totally, state-of-the-brain-damaged-art configuration interface? I was made a couple of times to try to fix IIS problems and damn, is that one misguided abomination if I ever seen one. I dunno - maybe they should make it - you know - well commented plain text configuration file? Or even XML? I heard this works for others ;) But all in all - ASP.Net aside (I have not yet encountered that closely enough, knocking on the wood) is there a reason to use IIS at all? Apache for Win32 works perfectly well. And the fact that IIS runs ASP (classic) is IMO a good enough reason to _disallow_ IIS usage anywhere you have authority to. (In my repeated experience a semi-intelligent ASP programmer with zero PHP experience is made 3-10 times more productive within a week of PHP exposure).
I don't know about you...but being an ex-ASP developer, I always found IIS to be rather bloated and testy. Even when I started using .NET and IIS 6 on a 2003 server...it still felt like bloatware! Give me an Apache server any day! :)
Jeff Whitfield jeffwhitfield@gmail.com "I can learn to resist anything but temptation..."
They handle the case right now, and, frankly... they don't have a clue what went wrong with ASP engine!
As others have said, there are countless people who are running ASP sites on IIS. The fact that you encountered a quirk in an outdated hosting option is hardly surprizing. Most certainly your problem relates to some of the securing down of COM.
Hands up those of you who think this will be nice and secure, and won't have any flaws. Hands up, all of you - cmon, I can't see any hands up.
The best thing they could do is run it on a different port, so that (with correct firewalling) it would only be accessible from the company admin ranges.
Get your own free personal location tracker
.. that they're making it more like Caudium.
Modular. Check (Caudium is *way* more modular than Apache.)
Web-based admin via SSL. Check
Integrated language for dynamic pages. Check.
Usually it's people with no real programming experience that seem to prefer PHP over .NET.
If you have any experience what so ever in general development you'd realize that loosely typed variables are very much a bad thing and that what PHP claims as OO doesn't even come close to the real deal. PHP's programming practices are something that just encourages hacking away at it to make up for bad design and invites bug-ridden, impossible to debug code.
It's also very much lacking a framework to do some decent componentization and even PHP 5 manages to stay years behind with no support for SOAP or any of the WS-* technologies and OO manages to be a factor 2 to 3 times slower than it was in PHP 4 already.
PHP is popular because it's cheaper to find hosting for and because 99% of the sites out there use pre-written scripts.
PHP does have some really nice features but to me they just melt away as soon as you try to build a site with some degree of complexity. It's great for a small to large hobby site, but that's really about it.
Lastly, for something that's generally accepted to be open-source, it's a remarkably expensive platform to develop for. $300 for Zend Studio, $2400 for Zend Encoder and/or Zend Accelerator for $300/year.
I don't think "stealing" is a very good word to use, or you start to fall into the same trap that a lot of people accuse organisations like the RIAA and MPAA of. ("Stealing" music, copyright "theft", etc.) That is, unless you agree with them that use of another person's ideas without asking is theft.
Personally I think it's good that Microsoft has finally decided to implement what everyone else has, for a long time, known to be useful. Just because Microsoft has done it doesn't mean that everyone else must stop doing it.