Andreas,

> how to handle the situation. It would be much simpler if you could rely
> on the OS to handle these things for you if it pulls away the carpet
> under your feets ;-)

    Take my advice, don't rely too much on the OS (got it ;-)

    Otherwise, don't stand on the carpet ;-)

    Cheers,

    PhiHo.

----- Original Message -----
From: "Andreas Raab" <Andreas.Raab at gmx.de>
To: <squeak-dev at lists.squeakfoundation.org>
Sent: Wednesday, September 11, 2002 1:07 PM
Subject: RE: Win Squeak needs to know about waking up! (Re: Laptop
suspending and network drives)


> Ned,
>
> > What about the WM_POWERBROADCAST message (at least for non-WinCE
> > apps)?
>
> You missed my point entirely or perhaps I didn't make it clear enough.
> Of course there are ways of getting notified (there always are) in the
> VM about a startup but what should the VM do?! It doesn't know enough
> about the resources associated (like, for example, what files are open
> and where the files come from) nor does it know about how to handle this
> situation in the context of some application or other. E.g., even
> assuming that we'd be enumerating the entire object memory to find all
> the file handles, do we actually know which ones to reopen?! Do we know
> how to handle failure situations?! Do we know if it's appropriate to
> reopen a network connection or not?! At the VM level, we just don't. And
> that's the problem. So the best I could eventually do is to pass some
> notification up to the Squeak level. But even then it's not always clear
> how to handle the situation. It would be much simpler if you could rely
> on the OS to handle these things for you if it pulls away the carpet
> under your feets ;-)
>
> Cheers,
>   - Andreas
>
>