ok last night I went out to a main stream mixer. you know to keep on top of what is going on in the tech industry. well I was shocked and amazed by the number of people using NT and ASP set ups. and of course they were telling me how great and wonderful it was and how no one writes HTML by hand any more and PHP was off the back... so I started to tell them what I did and how much trafic I run on my server (and I really don't run that much trafic at all) they tried to corect me "no you mean server hits, not uniques" and I very plolitly said no this is the adult world and I do mean uniques. LOL it was funny to watch as they picked up thier jaw from the floor :D

any way my question for every one is, how many of you out there actualy use ASP over PHP?

-Q

money money cash dough money muhla

I didn't vote because my choice wasn't up there....

I use ASP here at my day job and because of that, on my windows server I also run some ASP apps.

Because most of my stuff is up at M3 on linux boxes, I also started writing php stuff... I have since loaded php and mysql onto my windows server also...

Then I also run some custom cgi apps throgh my own CGI executable....

:)

My preference at the present time is php... if that helps



Last edited by sarettah at Jan 22 2003, 06:10 PM

Sorry sarettah...thats all I managed to read ;)

:agrin:

I developed ASP applications for about 3 years and I can honestly say it's awesome for closed environments with limited users. It's very easy to integrate Windows software such as word, excel, etc. into internet applications. The downside is that the security is horrible which is why I say it's great for closed systems, i.e. an intranet. I don't know much about PHP but I would say anything that runs on a Unix platform is a better choice from a security standpoint alone.

Microslop might be good for a desktop, but when it comes to load, nothing from their side of things can handle a volume of surfers. Heck, even some of Microsoft's critical high volume stuff runs on apache / unix combo, rather than IIS and NT...

ASP is fine for low volume stuff, but throw a pile of surfers at the problem, and you are fast fighting a losing battle... IIS goes to crap early, and ASP is resource heavy...

... and I am a windows programmer, and I won't touch the stuff much anymore.

Alex

I use AuthentiX ASP by Flix - seems good and stable, but never had massive loads to deal with.

Is this Alex from BSP?


Microslop - funny!

Nope. Alex as in Raw.

Alex

Editing as we speak


money muhla bread coin whatever you call it.... The mating song of the adult male nickatalinx

:agrin:

Thks sarattah :)

Waht do you use, Nicki? :matey:

Different tools for different jobs...

In the adult world for simple database driven dynamic content, PHP and MySQL are tough to beat...

There is something with a bit more "ooomph" out there: J2EE However, the learning curve is pretty hefty on it, part time programmers working out of the basement will struggle with it. Consequently the development costs are pretty high, but if I were doing something like....oh, say...a transaction engine that needed to handle some major league volume, that's what I would use.

That's what Perl is for. B)

Why would anyone run their webservers on a Windows Platform? Please tell me WHY? It makes me want to CRY :cryin:

I just took a mainstream site over and changed it from ASP to PHP. It wasn't like a port, I didn't have the ASP source I just copied the graphics and made up my own code to do the job. I was having problems at first so I asked the old guys tech what sort of gear they used for it before, he wrote:

"We are running the site on two boxes, one of which is dedicated to the
database the other is acting as the web server. Both are pretty high specd
machines with 4 CPUs each, though you probably could get away with one box and two CPUs running both the web server and the database."

Well I went away and sorted out a few bad bits of code, installed APC cache the sites now cranking away on a single 1GHZ CPU FreeBSD box with 512mb ram, load averages: 0.16, 0.13, 0.09.

FreeBSD, Apache, PHP, MySQL is all free so why bother with Microsoft!

I use Linux/Apache and mostly PHP.
ZMASTER's shopping cart is now PHP and it is fast as a MOFO.

My Perl programs are slowly being replaced with PHP.

ASP is old.

ASP.NET has many more advantages.

Why would anyone run their webservers on a Windows Platform? Please tell me WHY? It makes me want to CRY :cryin:[/b][/quote]
lololol.... (money cash green stuff bread <------- for Nick)

Well, in my case, I'm a whore...

I will program on whatever box someone pays me to program on...

Mine is not to reason why, mine is just to code, collect and get the fuck on to the next project......

At home, I am using my personal PC as a webserver.. I have that in Windows because my graphics card does not talk nicely to nix and I like to be able to tune into the tube when I'm working :) Also, my daughter likes to play her Barbie games on the same box... lol.... It is mainly my test server, but I also have some sites running from it :)

Why would anyone run their webservers on a Windows Platform? Please tell me WHY? It makes me want to CRY :cryin:[/b][/quote]
I think the real reason more often than not is because Windows is what a company knows. It's what their desktops/lan are on. They already have admins to run NT/2000, so IIS is familiar to them while Unix is scary.

There are a few applications where it makes sense to consider an NT based webserver....most of them are in an intranet, closed environment. One example would be departmental intranet servers where you want to restrict access by department or individual. If you do it on IIS, you can use the same NT logins that users use to access the network to authenticate them for the website, setup access groups, etc.

My preference is FreeBSD with Apache, PHP, Perl and MySQL...but I'm also a whore, we'll code in COBOL for enough money...heh.

ASP is great, .NET is awesome.

Nothing wrong with IIS5, 30k - 50k uniques per hour with minimal resource usage.

Most Windows programmers are sloppy, they are brought up that way. Thus the stories of IIS not being able to handle high loads. Every OS has its tricks, if you know them you can design around them.