Thanks, Reid. I realized that I can also switch SuperImage to bind to a bitmap, rather than a url, and if I load the image using an HTTPService I will have more control over HTTP responses. Of course, if I wanted to re-use the flex code outside of the HTML app, then I might be better off implementing something like your suggestion. Not sure yet what the best practice is here.
On 9/26/07, Reid Priedhorsky <[EMAIL PROTECTED]> wrote: > > > > > > > Richard Rodseth wrote: > > My flex app lives within an HTML app. I need to inform the user when > > the session has timed out, and redirect them to login. I'm interested > > in strategies for handling session timeout, and I also have a specific > > question about SuperImage. > > > > One of the places the app contacts the server is simply the url of a > > SuperImage component. mx:Image has the ioError event. In the timeout > > case, this event gets dispatched. Is there a SuperImage equivalent? I > > haven't checked the SuperImage source yet, but thought someone else > > might have gone down this path. > > Hi Richard, > > Here's a solution for managing timeouts on the client side: > > http://flexed.wordpress.com/2007/04/16/clientuser-idle-timeout/ > > I haven't used it myself, but we have it on our to-do list. > > Good luck, > > Reid > > > >
