Is Flex Session Tracking browser compatible?

I have implemented Flex Session Tracking it works fine with
Internet Explorwer browser but it does not work with Mozilla? Is it
not browser compatible?

Is it possible for you to send me your session tracking
codes, bcoz im also doing session tracking.
thanks

Similar Messages

Session Tracking in Flex

Hi All,
I need a simple session tracking application. this
application should include the following
1) Each user should have a seperate session area where each
user can store some info into it and retrive it.
2) Know how many users have logged into the application.
I come from j2ee background where these things are possible,
so requiring the same for my application which involves multi user
environment.
If not the application some part of code/ ideas will be higly
appreciated.
Thanks in Advance to all,
Vijay Karthik

Hi Avinash,
Put a status variable in the ModelLocator class(If you are using any Model class where your data can be accessed globally through out the application).
Once the user is authenticated and logged in successfuly update the status of the variable and you can authorize based on this status variable whether
the user is authorized to see the pages or not...
Thanks,
Bhasker Chari

Session tracking and Internet Explorer

Hi,
I am currently maintaining a servlet application, on apache/jserv.
This application implements a session tracking using a shared static hashtable of session data, associated with session id's.
This application may open more than one client browser windows.
With netscape, no problem.
With Internet Explorer, since the version 6, when the client close at least one window, the session is closed.
Thus, the application reject any new request from this client, sent by still open windows (session cannot be retrieved in the hashtable).
Has somebody heard about this problem ?
Thanks for any answer.

Thanks.
In fact, I believe that IE keeps the same session for
child windows.
The problem is: when you click on a link which open a
new window, the new open window share the session with
its parent window.
When the new window is closed, the session is also
closed.
It appears that this mechanism only exists since the
version 6 of IE.No. Earlier IE version handle session cookies the same way.

URL Session Tracking

Hi,
i want to make a group of JSP pages in a Web App, but assuming that the browser doesn't accept cookies.
Is there anyway that i don't have to indicate every link as
response.encodeUrl("index.jsp")I've heard something about a <url-session-tracking/> tag, but i've tried to put in the web.xml file, but it doesn't work.
I just want to put Index and the App Server takes care of putting the jsessionid info in front of the url
Thank you

Cancelling this question.

Always use URL Rewriting for session tracking?

All you JSP guru:
I am working on a JSP project that requires session tracking. I have successfully implements session tracking with both cookies or URL rewriting. I know that with the HttpSession object, it will always try to use cookie first, if that's disabled, then it'll automatically switch to URL rewriting. However, is there a way to force the HttpSession object to ALWAYS use URL rewriting instead of cookies? I have searched for an answer for a long time and haven't been able to found a solution. Is it possible at all? Thank you very much.

i was going to say that WebSphere always uses URL rewriting if you enable it at all, but someone beat me to it (indirectly) :-)
however, that seemed to me to be a violation of the spec, which seemed to imply the behaviour you're describing (only use URL rewriting if cookies are not supported on the current client)
here's a response someone else made on a websphere newsgroup to a statement in that regard:
I believe you are technically correct. However from my
experience, I think the spec if flawed in this area since
there is no reliable way of determining whether the
client browser supports cookies. The authority on
cookies (www.cookiecentral.com) says:
"To properly detect if a cookie is being accepted via
the server, the cookie needs to be set on one HTTP
request and read back in another. This cannot be
accomplished within 1 request."
This is asking too much of a servlet engine
implementation. Even if it did submit a request for this
purpose, the user could refuse the cookie. So
then technically the browser supports cookies, but the
servlet engine infers it doesn't. So if the servlet engine
infers the browser does not support cookies and so
encodes the URL, it is again out of spec because the
browser really does support cookies. By doing it
however encoding is configured makes things simpler,
robust, consistent and avoids the flaw.
My opinion.so, mostly i'm just rambling, but if you're using websphere, you should get the behaviour your boss wants. if you're using something else, i suppose there's a chance it'll "violate" the spec in this same, potentially helpful way.
btw, i remember somebody else complaining that URL rewriting is less secure than cookies, but i kinda think they're about equal. it seems like either could be intercepted by a sniffer and then used to spoof. but i'm no expert in that stuff...

Disable non-SSL session tracking?

Hi, all,
I wonder if one can disable all session tracking in JSP's whenever SSL is not being used? I would like to turn off all cookie-setting and URL-rewriting and use SSL-session tracking only (if I use session-tracking at all on a given page). I also want to specify this behavior programmatically (inside my JSP's) and not in my server's config files.
I'm basically concerned that if my user leaves one of my HTTPS pages, they will still retain a non-secure cookie with their session information. This seems to be indeed the default behavior: when I run my tests and transition from an HTTPS page to an HTTP one, the browser does store a cookie. I know I can invalidate the session as the next step, but I'd rather have the cookie not being set altogether to begin with. Imagine the situation where the user leaves my HTTPS page for a totally different (HTTP) website: in this setting I won't get a chance to invalidate the session and delete the cookie.
Any ideas, therefore, on how to programmatically disable non-SSL session-tracking?
Thanks,
Dmitri.

I don't think you can do this programatically.
However I also don't think it is a problem.
Cookies are related to zone names aren't they?
http://mysite and https://mysite are two different
zones as far as cookies are concerned. One should
not be able to see the other.
It issues a new cookie for the http site you are just
navigating to. That cookie has nothing to do with
the secure site you just came from, and shouldn't be
able to tell them any info about the secure site.
I think you are worrying about something that isn't
really there.
What is your concern? That they pick up a JSESSIONID
from the cookie and can then pretend to be a
different user?Yes. A cookie is transmitted and stored unencrypted, I imagine (in any case, it should be more easily crackable than SSL). I wish Sun came up with an extension to the Session API where you would be able to explicitly specify which session-tracking protocols you want used and which ones you don't. At the moment their API abstracts and manages too much detail for you.
I mean, if my site is supposed to be secure while I'm using SSL, then you'd expect that no information about those secure sessions should leak outside the SSL protocol, wouldn't you say?

Session Tracking problem

I am doing session tracking in jsp. what my purpose is i want to stop the user, if the user is already logged in.
For this, i am creating a Hashtable and entering the user id and session id as key- value pairs into the hashtable when the user is loggin in, if not in the hashtale. If these values are already in the hashtable, i am restricting the user.
when the user selects the log out option, i am invalidating the session and deleting the values in the hash table. this is working fine.
What my problem is suppose if the user closes the window, the session will be expired. but,i am not able to delete the values which are in the hashtable.
and if the user is trying to log in, according to my logic it is allowing the user.
Thanks
Anupama

i hope this would add-up to others' suggestion, albeit, i would recommend a bit change:
Given:
a. you're already implementing a session object that has pair value of user id and session id;
b. you want to restrict a user who previously logged-in but, say he/she accidentally or intentionally closed the browser, thus leaving his session object in the hashtable
Proposed Solution:
a. change your pair value from user id-session id to user id-passwd;
Explanation:
a. i believe that you maintain a user bean (with session scope) all throughout the web application;
b. i also believe that at the same time, you maintain other beans of the same scope, but that's out of question;
c. putting a session id will give you difficulties in validating a common user that previously logged in because each time a user logs-on, you generate a unique session id;
d. therefore, you cannot test equality of newly logged user and his new session id with that of his previous in the hashtable (if case pertains to abnormal browser termination);
e. changing a pair to user id and passwd will enable you to really trap and test if the new user has unterminated or invalidated session in the hashtable;
f. now, if previously logged user (with session still in the hastable) logs for the second time, you may invalidate his old session and give him a new session.

Looking for an expert on session tracking

I've got some session code running on RH linux using Apache and Tomcat. About 7% of my users experience a session variable not being present after a <jsp:forward> (or sendRedirect). I was thinking that it was related to cookies and how sessions are tracked, but I am using both the default cookie session tracking as well as URL re-writing; when I turn my browser's cookies off, I start seeing the jsessionid being used and everything still seems to work ok.
Is there anyone out there who might be willing to help me figure this pup out...why 7% of my users can't be tracked (session.getAttribute() doesn't find something that was placed into the session directly before the redirect/forward)?
/paul
[email protected]

OK, I've done a bunch of debugging. It appears all the folks who experience a "loss of session" have a URL with no parameters...even though I now parameters where passed.
Also, in some cases, the new URL that is being visited is accessed via either a <jsp:forward> or javascript's window.open.
Anyone know why some browsers might not pass parameters?

What is session tracking in servlets?

Hi ,
I'm studying servlets I don't have the clear idea about session tracking and Why and where we need to use it. Can any one say about this.....
Thanks in advance,
Maheshwaran Devaraj

Well Mheshpmr session tracking in servlets is very important...There are a number of problems that arise from the fact that HTTP is a "stateless" protocol. In particular, when you are doing on-line shopping, it is a real annoyance that the Web server can't easily remember previous transactions. This makes applications like shopping carts very problematic: when you add an entry to your cart, how does the server know what's already in your cart? Even if servers did retain contextual information, you'd still have problems with e-commerce. When you move from the page where you specify what you want to buy (hosted on the regular Web server) to the page that takes your credit card number and shipping address (hosted on the secure server that uses SSL), now let me tell you, how does the server remember what you were buying?
Well There are three typical solutions to this problem.
1. Cookies. You can use HTTP cookies to store information about a shopping session, and each subsequent connection can look up the current session and then extract information about that session from some location on the server machine. This is an excellent alternative, and is the most widely used approach. However, even though servlets have a high-level and easy-to-use interface to cookies, there are still a number of relatively tedious details that need to be handled:
* Extracting the cookie that stores the session identifier from the other cookies (there may be many, after all),
* Setting an appropriate expiration time for the cookie (sessions interrupted by 24 hours probably should be reset), and
* Associating information on the server with the session identifier (there may be far too much information to actually store it in the cookie, plus sensitive data like credit card numbers should never go in cookies).
2. URL Rewriting. You can append some extra data on the end of each URL that identifies the session, and the server can associate that session identifier with data it has stored about that session. This is also an excellent solution, and even has the advantage that it works with browsers that don't support cookies or where the user has disabled cookies. However, it has most of the same problems as cookies, namely that the server-side program has a lot of straightforward but tedious processing to do. In addition, you have to be very careful that every URL returned to the user (even via indirect means like Location fields in server redirects) has the extra information appended. And, if the user leaves the session and comes back via a bookmark or link, the session information can be lost.
3. Hidden form fields. HTML forms have an entry that looks like the following: <INPUT TYPE="HIDDEN" NAME="session" VALUE="...">. This means that, when the form is submitted, the specified name and value are included in the GET or POST data. This can be used to store information about the session. However, it has the major disadvantage that it only works if every page is dynamically generated, since the whole point is that each session has a unique identifier.
Servlets provide an outstanding technical solution: the HttpSession API. This is a high-level interface built on top of cookies or URL-rewriting. In fact, on many servers, they use cookies if the browser supports them, but automatically revert to URL-rewriting when cookies are unsupported or explicitly disabled. But the servlet author doesn't need to bother with many of the details, doesn't have to explicitly manipulate cookies or information appended to the URL, and is automatically given a convenient place to store data that is associated with each session.

Multiple Browsers & Session Tracking

when I start a separate (IE) browser and access a session tracking web app, I get a new session started. How come?
Many thanks in advance
Akz

start a separate IE browser how? double-clicking the IE icon on the desktop or the start menu?
If so, it's cuz doing that starts the new browser in a new process with separate memory usage and session cookies and all that separate from the other browser.
Netscape and most other browsers dont' do this, actually.

How to kill session on browser close

Can anyone tell me, how to invalidate the session on browser closes. I am using Internet Explorer as
browser.

Hi anmol10
if evnafets is to be believed, there is no 100% surefire way to do this. This is doing my head in a bit - I refuse to believe that there isn't some way around this.
I've been trying all kinds of things, kicking off threads that keep track of the sessions etc, but to no avail.
Let us know if you think of anything!

Calling an URL/Hyperlink in new session on browse from button.

Dear experts!
I created a Z program on SAP GUI, and configured the logical link for this program and call it from Web UI Client. In component BTCUSTOMER_H, i redefined DO_PREPARE_OUTPUT to maintained a button called 'FORWARD'. I create method EN_ONFORWARD to process. My problem is: on component BTCUSTOMER_H, when i click on FORWARD button, a new session on browse appear and display the Z program above or navigate to my Z program ( i can navigate to a standard transaction for example: from an Opportunity, i can maintain a button and navigate to a SaleOrder by click to this button). When i searched on forum, i found some thread said about this problem but i still can not resolve my problem. Can any one show me the details, how i configure for the Z program and processing code in method EH_ONFORWARD to resolve my problem.
Can anyone help me, please!
Longnd.

Hi,
Please follow the steps for calling you logical link.
When you create a Logical Link, you also should give the Target ID.
Now In the Naivigation Bar Profile you will have some thing called as Define Geniric OP Mapping
Here add a entrty with any Name , and give your target ID here.
For eg : ZCall_ZREPORT :Target Id ; Given in the step 1.
And in you even handler of the button write the followng code.
DATA: lr_nav_descr    TYPE REF TO if_bol_bo_property_access.
DATA: lr_navigation TYPE REF TO if_crm_ui_navigation_service.
DATA: lr_col          TYPE REF TO cl_crm_bol_bo_col.
cl_crm_ui_descriptor_obj_srv=>create_ui_object_based(
    EXPORTING iv_ui_object_type   = ZCall_ZREPORT
              iv_ui_object_action = 'B'
    RECEIVING rr_result           = lr_nav_descr ).
CHECK lr_nav_descr IS BOUND.
lr_navigation = cl_crm_ui_navigation_service=>get_instance( ).
CHECK lr_navigation IS BOUND.
Check whether navigation is supported
IF lr_navigation->is_dynamic_nav_supported( lr_nav_descr ) NE abap_true.
    RETURN.
ELSE.
    CREATE OBJECT lr_col.
    lr_col->if_bol_bo_col~add( iv_entity = lr_nav_descr ).
    lr_navigation->navigate_dynamically( lr_col ).

A Flex App in browser is a swf file or translated to Javascript

A Flex App in browser is a swf file or translated to Javascript?
Like Flash web site plugins [not whole browser window], exist and Flex plugins?
These are both swf files only without other supporting files?

A Flex app is a SWF and is not translated to Javascript. Many Flex apps do
use Javascript to handle history management and startup focus.

Flex session replication among cluster Help needed!

Hi,
I'am using Flex 3, LiceCycle Data Service 2.5.1, JBoss 4.2.1 in a web application. Our JBoss servers are in a cluster. We want to replicate Flex session among cluster, but it doesn't work. Did someone face issue with Flex session replication among application servers?
Thank you for your help
Gerard

Gerard, You will need to cluster the LCDS 2.5.1 instances the same way you clustered JBoss. Check out the "Configuring Data Services" chapter in the Admin guide: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/lcds/services_config_4.html -- Tom Jordahl Adobe <[email protected]> wrote > Hi, > > I'am using Flex 3, LiceCycle Data Service 2.5.1, JBoss 4.2.1 in a web > application. Our JBoss servers are in a cluster. We want to replicate Flex > session among cluster, but it doesn't work. Did someone face issue with > Flex session replication among application servers? > Thank you for your help > > Gerard

Can we use an overloaded constructor of a Java Bean with Session Tracking

Hi Friends,
If any one can solve my query.... It would be helpful.
Query:
I have a Java Bean with an overloaded constructor in it. I want to use the overloaded constructor in my JSP.
1. One way of doing that is to use it directly in the "Scriptlets" (<% %>). But then I am not sure of the way to do session tracking. I think I can use the implicit objects like "session", "request" etc. but not sure of the approach or of the implementation method.
2. Another way is through the directive <jsp: useBean>. But I cannot call an overloaded constructor with <jsp: useBean>. The only alternative way is to use the directive <jsp: useBean> where I have to write getter and setter methods in the Java Bean and use the <jsp: setProperty> and <jsp: getProperty> standard actions. Then with this approach I cannot use the overloaded constructor.
Can any one suggest me the best approach to solve this problem ?
Thanks and Regards,
Gaive.

My first reaction is that you can refactor your overloaded constructor into an init(arguments...) method. Instead of overloaded constructor, you can call that init method. This is the ideal solution if possible.
As to the two choices you listed:
1. This is OK, I believe. You can use scriplet to define the bean and put it into session scope of the pageContext. I am not sure exactly what you meant by session tracking; whatever you meant, it should be doable using HttpSessionAttributeListener and/or HttpSessionBindingListener.
2. Agreed. There is no way that <jsp:useBean> can call a constructor that has non-empty arguments.
Please tell me how it works for you.

Is Flex Session Tracking browser compatible?

Similar Messages

Maybe you are looking for