Hi Dave, That is correct.
I know the AMF polling will keep the session alive and in the worst case scenario if there was a way to time out the subscription successfully e.g. like the idle-timeout-minutes setting for RTMP then at least the idle HTTP session clock would start ticking after that. Unfortunately the session-timeout property times out the subscription whether there is activity or not so this cannot really be used. If one was allowed to use the idle-timeout-minutes property for AMF channels as well as RTMP channels then this would be great. Once again thanks for the help. Regards, John --- In [email protected], "Dave Wolf" <[EMAIL PROTECTED]> wrote: > > Just so I understand compeltely, you would like a way to make the J2EE > HTTP Session expire after N minutes even though there is the AMF > polling going on which is keeping it alive? > > > -- > Dave Wolf > Cynergy Systems, Inc. > Adobe Flex Alliance Partner > http://www.cynergysystems.com > http://www.cynergysystems.com/blogs > > Email: [EMAIL PROTECTED] > Office: 866-CYNERGY > > --- In [email protected], "johnwalshdoon" <johnwalshdoon@> > wrote: > > > > Hi Seth, > > > > Thanks for the detailed reply. The issue I have with the J2EE security > > and AMF polling is that in order to pull the latest chat messages down > > to my subscribed consumer I need to have AMF polling turned on. My > > security is implemented using J2EE form based security whereby a HTTP > > session exists for the user after they login. > > > > The fact that AMF polling is on it then means that the HTTP session > > never times out on my J2EE application server as there is a constant > > poll to the server. I was hoping I could time out the polling on the > > destination using the session timeout setting described below but as > > you describe below this timeout setting doesn't necessarily monitor > > activity over the destination only server pushes down to the consumer. > > > > Any ideas on how I can still implement the J2EE HTTP session security > > while having AMF polling turned on would be great. > > > > Thanks for your help so far. > > > > Regards, > > John > > > > --- In [email protected], "Seth Hodgson" <shodgson@> wrote: > > > > > > Hi John, > > > > > > Would you mind providing a bit more detail/context regarding the > > issue you've hit with using J2EE security with AMF polling? > > > > > > The <session-timeout> (somewhat unfortunately named..) doesn't have > > anything to do with the FlexSession for your connection (either over > > HTTP or RTMP). It is a timeout for Consumer or DataService > > subscriptions to the destination, and it is based on the last time a > > message was pushed to that subscriber. So even if other components > > (RemoteObjects/Producers/etc.) in your Flex app are sending messages > > to this destination, if no messages are pushed to this subscribed > > Consumer within the "session-timeout" limit it will be automatically > > unsubscribed on the server. This is more likely when message > > headers/selectors or subtopics are being used because only a subset of > > general message traffic though the destination will be pushed to each > > subscriber. This timeout doesn't impact FlexSession, it just removes > > this specific "idle" subscription that hasn't been receiving any > > messages. Hopefully that helps clarify the documentation. > > > > > > Best, > > > Seth > > > > > > ________________________________________ > > > From: [email protected] [mailto:[EMAIL PROTECTED] > > On Behalf Of johnwalshdoon > > > Sent: Tuesday, November 21, 2006 7:54 AM > > > To: [email protected] > > > Subject: [flexcoders] Issue with "session-timeout" Network setting > > on Destinations with AMF Polling. > > > > > > Hi all, > > > > > > I have an issue with session timeouts at the moment regarding AMF > > Polling. Our application incorporates a 2 way chat component using an > > AMF channel with AMF polling enabled. The issue I have is that there > > is no way to integrate J2EE security successfully if you have AMF > > polling turned on. I have read all the very informative threads on > > this forum so I attempted a workaround. > > > > > > The work around I aimed to use was to set the network session > > timeout on the destination. Once this time elapses the J2EE app > > server HTTP Session will start ticking. This is all well and good but > > the session timeout on the network settings times out no matter what > > even if there is activity over the destination. This means that > > someone will be kicked out even if they have been using the > > destination. Is this a **BUG** ?? > > > > > > The flex documentation says -- > > > > > > session-timeout (Optional) - The session-timeout element specifies > > the idle time ! in minutes before a subscriber is unsubscribed. When > > you set the value to 0 (zero), subscribers are not forced to > > unsubscribe automatically. The default value is 20. > > > > > > Note the word idle is used in the documentation this leads me to > > believe this is a bug!!. > > > > > > Any help would be greatly appreciated. > > > > > >
