There are actually three timeout settings you may need to configure for FDS.  There is the HTTP session timeout which is configured via your app server’s settings.  That controls the session timeout for HTTP based channels as you would expect.  Any activity on the session for that web application will keep that session alive.  This includes the polling requests which are initiated by that client so if your polling interval is more frequent than your app server’s session timeout, your session will be kept alive.

 

There is the idle-timeout-minutes attribute for RTMP channels which determines the session timeout for RTMP based channels.  Any message sent or received over the channel will keep it alive.  This will timeout if the connection is left idle.

 

There is also the subscription timeout which you set for a given destination via the (poorly named) session-timeout tag underneath the network tag for that destination.  If you set this to 0, the subscription timeout is the same as the session timeout.   This is not the default though… It defaults to 20 minutes.   When this timeout expires, it sends a message to the client which tells it to unsubscribe from the channel.   When a consumer unsubscribes, it also disconnects from the channel.   So with the default session-timeout, a client which subscribes even using an AMF polling channel will get unsubscribed automatically which will stop the polling.  That will allow the HTTP session to expire normally. 

 

If you are using Data Management Services and your destination is unsubscribed due to the subscription timeout, it causes your DataService to be disconnected.  You can watch for properties change events on the “connected” flag or bind to that property on the DataService.  

 

So I think you are probably using the default and so can just watch for the connected property on your DataService to be set to false.  Any message like fill, getItem, or commit which you invoke on the DataService will cause it to reconnect automatically.   When you reconnect, the DataService automatically resubscribes for any fills, getItems or whatever which you have not explicitly released.

 

Jeff

 


From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Miller
Sent: Thursday, August 10, 2006 12:24 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] FlexSession expiration question

 

I have a managed Object (via FDS) which I need to update via
server-side push. Also, I have multiple clients that need to display
this up-to-date object. Everything works great untill I leave one of
the clients for 20 minutes or so after which the client stops
receiving updates from the server. I assume that this issue has
something to do with FlexSessions.
Is there any way to determine if there has been a timeout on the
client side?

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to