Unfortunately, we can't help but litter in this situation: we open a URLStream connection, and Flash Player (in Internet Explorer) does not drop the connection when the corresponding URLStream object is destroyed (I assume that it probably would drop the connection when GCing). This is a Comet-style connection that must remain open while the Flex application is running, so it's not something we can clean up "when we're done" without having access to an application exit event. The user killing the browser at any moment is not a problem for us, because in that case, the connection is dropped properly.
I'll try Sherif's Javascript suggestion, although I was hoping there would be something cleaner. --- Maciek Sakrejda Truviso, Inc. http://www.truviso.com On Sat, 2008-02-23 at 09:04 +0000, andrii_olefirenko wrote: > as there are no finalizers nor destructors, the same goes for > finishing the application. Don't litter, and there would be nothing to > clean up :) > It's important to keep in mind that a user could kill browser process > any time, without waiting for you code to do anything. > > Andrii Olefirenko > > --- In flexcoders@yahoogroups.com, Maciek Sakrejda <[EMAIL PROTECTED]> > wrote: > > > > I need to perform some cleanup when the user exits the application > > (i.e., closes the page in which the application is embedded). Is > there > > an event I can listen for? I've tried Event.REMOVED, > FlexEvent.REMOVE, > > and Event.REMOVED_FROM_STAGE, but none of those seem to fire > targetting > > the actual application object. Any ideas? > > -- > > Maciek Sakrejda > > Truviso, Inc. > > http://www.truviso.com > > > > > > >
