{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Ryan La Riviere <[EMAIL PROTECTED]>
On 02/07/2002 08:30, "Derek Balling" <[EMAIL PROTECTED]> wrote:
> 1.) "Reconnect to All"
>
> So I am logged in to 4 services at home. I close my laptop lid
> (sleep mode) throw the PB in the car and go to work. I open up and...
> Fire THINKS (for a bit anyway) that it's logged in, but it isn't. The
> ability to say "your network world is radically different, and you're
> not really connected, reconnect to everywhere you think you're
> connected" would be mondo cool.
I was thinking of something a little more robust than that. When you switch
networks like that you're most likely going to get a different IP address
(unless you use a static IP at least one location) which I would think would
force Fire to realize it's on a new network but that's not necessarily
always the case. One thing I have to do when going from office to home and
back, is switch my network location settings (airport name and password not
same at both locations). So if Fire was able to wait at least 4-5 or so
seconds before attempting to reconnect, that would allow the network
settings (when there's user intervention) to settle.
The other half is making it so Fire is able to detect when there's not a
network connection. I *think* the system is able to provide this
(graphically one of my docklings is able to show me when there is no network
connection). That would allow Fire to be smart enough to wait to reconnect
until there is an active network connection.
The third part is the reconnect to all, IMHO, should only try to connect to
either what you were connected to previously or to connect to all services
that are set to auto-login.
That's my story and I'm sticking to it.
--
Ryan La Riviere
System Administrator; Drexel University
215.895.6010
<http://staff.tdec.drexel.edu/~edljedi/>
{#} ----------------------------------------------------+[ fire ]+---
