Win a copy of Modern JavaScript for the Impatient this week in the Server-Side JavaScript and NodeJS forum!

vijayakumar vivekanandan

Greenhorn
+ Follow
since Dec 08, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by vijayakumar vivekanandan

Thanks Ben.
15 years ago
Thanks Ben.
I am maintaining the Web app that is built long ago.
The checklist is to be followed when we are adding new pages as part of enhancement work. Also the application will be scrapped after an year. So the clients dont care much about that architect or architecture.

I understood your explanations except the following point.
Can you elaborate on this?

"It also helps to insure that the app will work in a distributed environment without having to set up session replication. "
15 years ago
Hi I have a requirement where in the URL displayed on the browser address bar should not change whatever link you click from page and however you navigate.
The URL displayed should always be that of the home page.

Also in the status bar instead of the link a title or static text has to be displayed when mouse is moved over link....

Ideas on how to do this are welcome.

Advanced thanks.
15 years ago
I believe you can do this with EL. ${Cookie.yourCookieName}. It will not return null if the cookie is not there.

Then you can use <c:if > tag to check if the resultant value is null. This means the cookie is not available.

<c:if test="${Cookie.yourCookieName = null}">

I am also a beginner to EL. Try implementing this.
15 years ago
JSP
The client for whom I develop Web application has given a checklist where in they say <%@ page session="false" %> should be mentioned in all JSPs. The checklist was prepared by an architect who is no more with the company.

Any idea why they prevent JSPs from participating in sessions.
15 years ago
The client for whom I develop Web application has given a checklist where in they say <%@ page session="false" %> should be mentioned in all JSPs. The checklist was prepared by an architect who is no more with the company.

Any idea why they prevent JSPs from participating in sessions.
15 years ago
JSP
Hi rodrigue,
But if the same attribute is available in the same name in more than one scope what will the "items" in the c:forEach refer???
This is found in JSTL 1.1 spec section 6.1.1.

I cannot understand the constraints mentioned for Enumeration and Iterator objects.

".... A large number of collection types are supported by <c:forEach>, including all implementations of java.util.Collection (includes List, LinkedList,
ArrayList, Vector, Stack, Set), and java.util.Map
Implementations of java.util.Iterator and java.util.Enumeration are
supported as well but these must be used with caution. Iterator and
Enumeration objects not resettable so they should not be used within more than one iteration tag."
Is the items attribute in <c:forEach> tag refer only to request scoped variables?
Thanks. It answered my question.
15 years ago
JSP
In what type of scenarios do we need to use buffer="none" in a JSP page?
why somebody will not want to use buffer. I believe buffering helps
in improving performance?

Is there any disadvantage of using a large buffer size in the page?
What are the security problems when we use cookies?
Why do some corporates/users disable cookies in their browser?
15 years ago
why do we need two seperate functions
encodeURL(String url) [ for normal encoding of URL with sessionID]
and
encodeRedirectURL(String url)? [ for redirect scenario encoding of URL with sessionID]
Can't a single method do encoding for the normal and the redirect case?
1) Browser cookie support enabled.
Request first sent & server sets the session ID as cookie in the HTTP response header.

2) Browser sends the cookie back while making the next request to the server. Now the server picks up sessionID cookie and thus the client joins the session.

3)
Response sent with session ID as cookie and not URLencoding since you found that cookie was enabled last time.

4) All of a sudden Browser cookie support disabled.
So what will happen now since for next subsequent request cookie disabled and also url is not rewritten with sessionID in the html response we got from the server. So will that session be lost?

Do we have any protection against this scenarion?
1) Browser cookie support enabled.
Request first sent & server sets the session ID as cookie in the HTTP response header.

2) Browser sends the cookie back while making the next request to the server. Now the server picks up sessionID cookie and thus the client joins the session.

3)
Response sent with session ID as cookie and not URLencoding since you found that cookie was enabled last time.

4) All of a sudden Browser cookie support disabled.
So what will happen now since for next subsequent request cookie disabled and also url is not rewritten with sessionID in the html response we got from the server. So will that session be lost?

Do we have any protection against this scenarion?
15 years ago
JSP