When should I use ASP etc?

[Michael]

Having just about got to grips with HTML, I am now looking to broaden my horizons with some web programming.

Can someone please tell me what are the relative merits of JavaScript, VBScript, CGI, ASP, PHP3, etc?

Under what circumstances should you use one of these particular facilities?

What is the decision-making process when deciding which to use?

I realise that my question is broad enough to write a thesis on, so any web site references would be welcome.

Thanks in advance.

[Mark Sreeves]

OK here's a starter:

JavaScript is used in client-side and does all sorts of usefull/fancy things. Such as verification on data before it is posted back to the server.

ASP only runs on Microsoft Web Servers (which may or may not cost you money)

VBScript can be cleint-side or ServerSide but it is better only to use it on the server and use Javascript in browsers

JavaScript can also be used ServerSide in Active Server Pages


CGI offers an interface between trhe server and applications running on the server


PHP3 runs on Appache servers and others I expect but I've never used it and someone else will enlighten you as to its merits other than Appache is free run on Linux (also free)

Server-Side Javascript is a particluar flavour of Javascript used on Netscape Servers which are free I think - perhaps I ought to read the EULA (this is NOT the same as using Javascript in ASP)


So, for code in a browser use Javascript

and choice serverisde language depends on which server you are using which depends on which type of server suits your needs at the price you want to pay!

[Michael]

Thanks for that - I get the feeling that we are just scratching the surface here!!!

What sort of applications would each type be most suitable for?

[Michael]

This post is to get me to the top of the list in an attempt to provoke an answer!!!)

What sort of applications would each of JavaScript, VBScript, CGI, ASP, PHP3 (or any of the other poular acronyms!) be most suitable for?

[Skeen]

Whether you need specific security on a page ie a loggin to a database, or you are using dynamic code that requires no real security, should determine what kind of scripting is needed. On server side applications, all script is hidden from the user, but use of cookies etc is required in many instances, but if the scripting is of no real concequence in terms of security to the integrity of the site, client side applications would generally be less complicated and quicker and therefore the obvious choice.

[kurtsimons]

Order of operations.....

learn HTML

then JavaScript

Then a server script language
PERL

then
ASP or JSP

(if you learn ASP and then try to learn PERL you will hate perl so much you won't even try. But perl runs on UNIX ASP doesn't.)

then learn a programming language such as VisualBasic to create apps that can drive PerlScripts or Send generated files Via FTP to a web site to be executed by a Script or directly by the server to return HTML to the client that can have further client side functions by the use of JavaScript.

Its all one big mess of crap, and just when you think your done something doesn't work!

[Michael]

"Its all one big mess of crap" - Yes Kurt - this is the message that is coming through to me!!!.

Where does PHP fit into the grand scheme?

[tonyenkiducx]

I say, learn HTML, learn ASP(Which is either VBScript, or JScript(Not Javascript which is an entierly different thing)), then learn either access, or SQLServer depending on how cheap you are(Both use the SQL language, so dont worry about changing later). Dont be told by these unix spods that you HAVE to learn PERL, Ive used it loads, and as a server side app its shite, leave it set aside for writing little unix apps, and not generating webpages. PHP isnt bad, but its still in its infancy, and mySQL(Unix version of sql server), is crap as well(Distributed WHAT?). And if you really want to argue the unix point, IIS5 comes with a link to download perl for IIS, and vice versa, ASP for apache does exist(If not in a cut-down, incredibly slow form).

[TEST]

Learn HTML and you can create a static webbpage. Learn DHTML and JavaScript and you can create a dynamic webbpage and give it a nice look. Learn SQL and ASP (preferebly VBScript) and you can create a nice webbpage that's both dynamic and interactive. You are, however, limited to an IIS-webbserver (NT) but that's not really a problem. If you've come this far you can make a good living of your knowledge. If you truly want tp go for it you skip ASP and VBScript and go for VB7 and ASP+ 'cause that's where the future is! This is the "Microsoft"-track. You could choose the UNIX-track and go for PHP (which is the same as ASP but on UNIX) or you could skip everything above and go for pure Java only!

Best regards,
Peter Hammar
http://www.mogul.com

[Michael]

Thank you all for your advice and I have no doubt that it is well-meaning. However, we seem to have lost track of the original question, which was .....

What sort of application is each of these facilities best for and what is the decision-making process when deciding which to use?

[tonyenkiducx]

Micheal,
I think the underlying message from everyone here is that you should learn HTML, then a browser scripting language(VBscript, or javascript), then a sback end cripting language(ASP if your on window, PHP if your on unix) with a database (SQLServer onb windows, MYSQL on unix), then a back end programming language(Perl for unix, VB for windows). There is no best app, and they all do pretty much everything, they are programming languages after all. just learn one of each, and make sure there compatible.