Ask a Pro

Balmukund replied | 4 days ago

Servlet methods

• init(): runs once when the servlet is first loaded, for setup.
• service(): runs for every request and decides which doXxx() method to call.
• doGet() and doPost(): handle GET and POST requests. There are also doPut(), doDelete(), doHead() and doOptions().
• destroy(): runs once when the servlet is removed, for cleanup.

JSP methods
A JSP is converted into a servlet, so it has similar methods:

• jspInit(): runs once at the start.
• _jspService(): handles each request. The container generates it, so you don’t write it yourself.
• jspDestroy(): runs once at the end.

Sadiq replied | 5 days ago

Yes, Scala is considered moderately to very challenging to learn, depending on your background and how deep you go into its advanced paradigms.

Why Scala Has a Learning Curve

• Dual Paradigms: Scala combines Object-Oriented Programming (OOP) and Functional Programming (FP). If you are only used to imperative or standard OOP languages like Java or C++, shifting to concepts like immutability, pure functions, and recursion requires a major mental shift.
• Complex Type System & Features: Features such as implicits, macros, higher-kinded types, and advanced type-level programming can quickly become dense and difficult to read or debug.
• Over-Engineering Risk: Teams sometimes struggle because developers write overly complex, academic code (like monad transformers and custom operators) that the rest of the team finds hard to maintain

Lata replied | 2 days ago

A website can remember your login even after you close and reopen your browser because of cookies and sometimes local storage — small pieces of data saved on your computer by the site.

Here’s how it works 👇

🧠 1. Cookies

• When you log in, the website sends a session cookie to your browser.

• If you check “Remember Me,” it also sends a persistent cookie that stays even after closing the browser.

• This cookie contains a unique token (not your password) that identifies you when you return.

• When you reopen the site, your browser sends that cookie back, and the server recognizes you.

💾 2. Local Storage or IndexedDB

• Modern websites may store login tokens or preferences in local storage or IndexedDB, which remain until you clear them manually.

• This helps keep you logged in or remember settings like language or theme.

🔐 3. Secure Tokens

• Instead of storing passwords, sites use authentication tokens (like JWTs).

• These tokens verify your identity securely and expire after a set time for safety.

⚙️ 4. Auto Login Process

1. You log in → server creates a token → browser saves it.

2. You close the browser → token remains.

3. You reopen → browser sends token → server verifies → you’re logged in automatically.

⚠️ Security Tip

If you’re on a shared or public computer, avoid “Remember Me” — anyone could access your account later.

Pulkit replied | 23 hrs ago

When you log in to a website, it often saves a small piece of information in your browser called a cookie. Think of it as a small digital ID card.

The next time you visit, your browser sends that ID back to the website, and the website recognises you.

That's why you don't have to enter your password every single time.

And no, your password isn't usually stored in that cookie. The website uses something called a session ID or token to verify that it's really you.

Of course, this depends on the website and how it manages your login.

So basically, the website isn't remembering you like a friend does. It's just using a clever little system to recognise you!

Balmukund replied | 02 Nov

JSP is still supported but is considered legacy, with little new development.

• Renamed: Java EE moved to the Eclipse Foundation and became Jakarta EE. JSP is now Jakarta Server Pages, with the package namespace changed from javax.* to jakarta.*. It still ships in Jakarta EE and in servlet containers like Tomcat.
• Maintained, not growing: It gets compatibility and cleanup updates (for example, removal of old features), but no major new capabilities.
• Replaced for new projects: Newer Jakarta EE work favours Jakarta Faces (JSF), Jakarta MVC, REST APIs with a JavaScript front end (React, Angular), and template engines like Thymeleaf or Freemarker (often with Spring Boot).
• Still in use: Many large existing enterprise applications run on JSP, so it will be around for a long time in maintenance work.

In short, JSP won’t disappear soon, but you wouldn’t choose it for a new project. Knowing it is still useful for legacy systems and interviews.

Balmukund replied | 02 Nov

Sadiq replied | 5 days ago