CODEWITHSUNDEEP
javascriptjavahtmljsp
Akuzuki29087
Akuzuki29087

Reputation: 33

HTML+javascript or javascript +jsp?

Hi I'm new to dynamic web dev. I've searched this site but couldn't find anything similar.

I want to implement a password checker, for robustness and length etc. Fairly conventional. The thing is, I have 2 options: 1. embed javascript inside an HTML. 2. embed javascript inside a jsp file.

With a little preliminary research it seems that most people recommend the former, that is to go with HTML. I wanna know why? I could be completely wrong, in that case I also wanna know why?

The "how" isn't all that important, but "why".

Edit: I know this question is full of flaws (for example JSP and HTML aren't mutually exclusive) but please indulge me a little bit and tell me which scheme is more appropriate, if I want to get things done front end, in a user's browser.

Edit#2 : Sorry I did not provide any bg information: I am working on a larger project and password checker is just a part of it, the project itself is a dynamic web project relies predominantly on java, serverlet.

Upvotes: 0

Views: 406

Answers (4)

Rush
Rush

Reputation: 137

If security is not a big concern then HTML + javascript should be fine. It will be responsive amd lead to better user experience. If this is an external facing application on the web then as mentioned in some of the other answers go with Jsp approach.

Upvotes: 0

samanime
samanime

Reputation: 26527

Depends on your use-case. In some cases, just the front-end is enough. In many, I would say both is better.

By putting it in the front-end/client-side (the "HTML"), you create a more user-friendly approach, since you can rapidly and continuously evaluate the users' input and give them feedback.

If the application doesn't need to be particularly robust from a security perspective, this can be plenty.

The downside of HTML only validation of any user input is that it can easily be bypassed. As a programmer, I could figure out what its doing and easily bypass any and all client-side protects. Users can also wholesale just disable JavaScript, so if your site works without JavaScript in general, they won't get any validation. This is why "security" on the client side is never a thing. Never trust the client.

Implementing it only on the back-end/server-side ("JSP"), you can lock down the security since the end-user can't bypass any of your validation. It must match the rules you set forth.

The downside to server-side is that you must send the data to the server to be analyzed, then wait for a response. While this may be fast, its still much slower than client-side.

By doing it in both, you get the best of both worlds. You get the rapid feedback for the end-user without having to send any data to the server, and you get the full protections of making sure it is properly validated on the server-side.

The downside to this of course is you have to double-up on your code, so its more effort. That's why you want to weight the pros and cons in your particular case, as there isn't a single "best" answer.

Upvotes: 1

philip
philip

Reputation: 345

As you state you are new to dynamic web dev. JSP is a server side programming language Just like PHP and others. If you want to confirm password, you can use ajax to check for a match from your database and if match was found create a session and redirect your user to the logged in page. If i misunderstood your question, please try to be clear enough.

Upvotes: 1

20 fps
20 fps

Reputation: 342

If the HTML is enough for you - why should you use .jsp?

You need .jsp for creating dynamic content and it's gonna be compiled as Servlet - do you actually need Servlet in this case?

Upvotes: 0

Related Questions