asp, php or jsp
 

Hello...
I want to design website for my project so any one here please tell me the programming language which i use so that my application is secure, no one able to hack that...

Re: asp, php or jsp
 

Almost guaranteed any application you write will be hackable one way or another no matter what language you write it in. Granted you should try to write it to not be.

You should consider why you need a language. Are you using dynamic content, http requests, a database, etc? If not then plain XHTML, JavaScript, and CSS might be the best way to go.

The key to choosing a language for a web app is to choose one that is best suited for what you need or what is available. Each language has pros and cons. I often use Classic ASP because I have to work with existing MS Access databases which would be much harder to use in PHP. If you are using a MySQL database then PHP or Perl are probably your best bets.

Overall I would recommend PHP, not because it isn't hackable, but because there are a lot of resources on the web to help you figure out how to do what you want to do.

Re: asp, php or jsp
 

As a professional development manager, and after working on a number of security projects, I'll take some exception to the above statement. There are a number of applications, either client server or web apps that have been designed and implemented to be very secure.

The problem is that people design security in AFTER the code is complete. The security problems and potential attacks need to be part of the initial design process. Security breaches are often via "back door" attacks, like leaving the FTP password "pswd", so attention also needs to be paid there.

I do agree with the statements that JSP, ASP or PHP should be chosen on the basis of what platform you are targeting and what your development skill set is. All will do a fine job, but think about security as you design not as an afterthought.

And there have been 100's of threads and posts on what language, web host, web site, etc to use. You might want to go dig through the massive CD archive to see what others have said in the past.

One of the things we do in the business side is have a "Build vs. Buy" conversation. Do we want to build things from scratch, or buy something off the shelf to customize. If you scroll down to the bottom of the page you'll see "Powered by vBulletin". In this case the vBulletin software does most of the heavy lifting, you don't need to reinvent the wheel (or reinvent ways to make the site secure)

Learning how to make a website from scratch using PHP, JSP, ASP is a good thing to know, but I'll tell you, none of my design teams start from scratch. We always pick a framework to build on, there are better uses of time than reinventing the wheel.

Good luck!

Re: asp, php or jsp
 

Only thing I'd add is that ASP is very old technology. ASP.NET is the current version and should be used for anything newly designed - and it's inherently more secure than ASP. You can get a free version of Visual Studio at Microsoft's site, and student pricing on the full set of tools is quite reasonable: http://www.microsoft.com/express/. I'd also mention that .NET programmers are very in demand in the industry :) so learning .NET is a good move from a career point of view. They even have a free robotics studio available that uses dot net.

On the build vs buy side I'd recommend looking into a content management platform for your website. There are a number of free open source ones including DotNetNuke, and Joomla. Be sure that you can get the hosting resources you need to run any platform you want - but you can buy a whole lot (like strong login security, etc.) by starting from a content management platform.

Disclaimer: My company is a Microsoft Gold Certified ISV so we are heavily Microsoft oriented here.

Good luck
Lee Drake
CEO, OS-Cubed, inc.

Re: asp, php or jsp
 

You are correct and I guess my comment was a little too general. I should have said that it is the programmer not the language that makes an application secure or not. Designing security in from the beginning and keeping conscious of it throughout the development cycle is important but there are so many things to look out for it is easy to miss something or not even know about something that you should know to look out for.

In reality the question should be how to write secure code instead of what language is secure.