|
Home > Archive > Macromedia Flash Server > August 2005 > netconnection.onstatus
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
netconnection.onstatus
|
|
| Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+w 2005-08-11, 5:46 pm |
| Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected, will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Graeme Bull 2005-08-11, 5:46 pm |
| It's not so bad, but it would be better to call a function that does the
shared object getting just to keep things all seperate. And you never know
what state your app is in when it is required to "reboot". Which would mean
making a decision on whether you need to connect up to the SO and what you
want to do with the data etc..
It really depends on the complexity of your application I suppose.
Graeme
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
Sent: Thursday, August 11, 2005 10:15 PM
To: FlashComm Mailing List
Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] netconnection.onstatus
Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected, will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+w 2005-08-11, 5:46 pm |
| I read somewhere that netconnection.onstatus has a sort of "built-in"
functionality to reconnect to the server if disconnected. Am I wrong? I
guess my question is, would "NetConnection.Connect.Success" change to
"NetConnection.Connect.Closed" and then back to
"NetConnection.Connect.Success", in which case everything within would be
executed again. Or, is it more seamless where a netconnection info object
isn't really even sent in this case?
Thanks again,
Brandon
"Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 10:03 AM
Please respond to
graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To
"'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject
RE: [FlashComm] netconnection.onstatus
It's not so bad, but it would be better to call a function that does the
shared object getting just to keep things all seperate. And you never know
what state your app is in when it is required to "reboot". Which would
mean
making a decision on whether you need to connect up to the SO and what you
want to do with the data etc..
It really depends on the complexity of your application I suppose.
Graeme
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
Sent: Thursday, August 11, 2005 10:15 PM
To: FlashComm Mailing List
Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] netconnection.onstatus
Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected, will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+w 2005-08-11, 5:46 pm |
| The application is super simple. One connection, one shared object, etc.
Thanks
"Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 10:03 AM
Please respond to
graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To
"'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject
RE: [FlashComm] netconnection.onstatus
It's not so bad, but it would be better to call a function that does the
shared object getting just to keep things all seperate. And you never know
what state your app is in when it is required to "reboot". Which would
mean
making a decision on whether you need to connect up to the SO and what you
want to do with the data etc..
It really depends on the complexity of your application I suppose.
Graeme
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
Sent: Thursday, August 11, 2005 10:15 PM
To: FlashComm Mailing List
Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] netconnection.onstatus
Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected, will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Graeme Bull 2005-08-11, 5:46 pm |
| nope, no built in functionality at all. If the connection goes down, you
have to watch for that and reconnect people up making sure to keep the state
of your app in mind when you go to reset values etc and reconnect to the
shared objects and streams.
Graeme
-----Original Message-----
From: Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
[mailto:Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org]
Sent: Thursday, August 11, 2005 11:30 PM
To: graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; FlashComm Mailing List
Cc: 'FlashComm Mailing List'; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: RE: [FlashComm] netconnection.onstatus
I read somewhere that netconnection.onstatus has a sort of "built-in"
functionality to reconnect to the server if disconnected. Am I wrong? I
guess my question is, would "NetConnection.Connect.Success" change to
"NetConnection.Connect.Closed" and then back to
"NetConnection.Connect.Success", in which case everything within would be
executed again. Or, is it more seamless where a netconnection info object
isn't really even sent in this case?
Thanks again,
Brandon
"Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 10:03 AM Please respond to
graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To "'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject RE: [FlashComm] netconnection.onstatus
It's not so bad, but it would be better to call a function that does the
shared object getting just to keep things all seperate. And you never know
what state your app is in when it is required to "reboot". Which would
mean
making a decision on whether you need to connect up to the SO and what you
want to do with the data etc..
It really depends on the complexity of your application I suppose.
Graeme
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
Sent: Thursday, August 11, 2005 10:15 PM
To: FlashComm Mailing List
Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] netconnection.onstatus
Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected, will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Bill Sanders 2005-08-11, 5:46 pm |
| Hi Brandon/Graeme,
I've been doing some work with disconnects and I found that if you
reconnect soon enough, the disconnect is never noticed. It's been
done where a WiFi connection may quit and then re-start. To determine
the amount of time you can have a disconnect, just pull the Internet
plug and plug it back in again to see if you get a state change. If
you don't, the disconnect was never noticed.
HTH,
Bill
On Aug 11, 2005, at 10:43 AM, Graeme Bull wrote:
> nope, no built in functionality at all. If the connection goes
> down, you
> have to watch for that and reconnect people up making sure to keep
> the state
> of your app in mind when you go to reset values etc and reconnect
> to the
> shared objects and streams.
>
> Graeme
> -----Original Message-----
> From: Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
> [mailto:Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org]
> Sent: Thursday, August 11, 2005 11:30 PM
> To: graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; FlashComm Mailing List
> Cc: 'FlashComm Mailing List'; flashcomm-
> bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> Subject: RE: [FlashComm] netconnection.onstatus
>
>
>
> I read somewhere that netconnection.onstatus has a sort of "built-
> in"
> functionality to reconnect to the server if disconnected. Am I
> wrong? I
> guess my question is, would "NetConnection.Connect.Success" change to
> "NetConnection.Connect.Closed" and then back to
> "NetConnection.Connect.Success", in which case everything within
> would be
> executed again. Or, is it more seamless where a netconnection info
> object
> isn't really even sent in this case?
>
> Thanks again,
> Brandon
>
>
>
> "Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
> Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> 08/11/2005 10:03 AM Please respond to
> graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
> FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
>
>
> To "'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
> cc
> Subject RE: [FlashComm] netconnection.onstatus
>
>
>
>
>
>
>
> It's not so bad, but it would be better to call a function that
> does the
> shared object getting just to keep things all seperate. And you
> never know
> what state your app is in when it is required to "reboot". Which
> would
> mean
> making a decision on whether you need to connect up to the SO and
> what you
> want to do with the data etc..
>
> It really depends on the complexity of your application I suppose.
>
> Graeme
>
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
> Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
> Sent: Thursday, August 11, 2005 10:15 PM
> To: FlashComm Mailing List
> Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> Subject: [FlashComm] netconnection.onstatus
>
>
> Might be a dumb question.
>
> I have the following:
>
> client_nc = new NetConnection();
> client_nc.onStatus = function(info) {
> if (info.code == "NetConnection.Connect.Success") {
> so = SharedObject.getRemote("soInfo", client_nc.uri,
> true);
> so.onSync = function(list) {
> //do something
> }
> }
> }
>
> Is it dangerous to put any sort of function inside the
> client_nc.onStatus?
> If a client is disconnected, and is then automatically
> reconnected, will
> "NetConnection.Connect.Success" be sent again, thereby initializing
> everthing inside the client_nc.onStatus a second time?
>
> Thanks,
> Brandon
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Graeme Bull 2005-08-11, 5:46 pm |
| I've noticed this too.. It's kinda cool.
Graeme
-----Original Message-----
From: Bill Sanders [mailto:wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org]
Sent: Thursday, August 11, 2005 11:59 PM
To: graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; FlashComm Mailing List
Subject: Re: [FlashComm] netconnection.onstatus
Hi Brandon/Graeme,
I've been doing some work with disconnects and I found that if you
reconnect soon enough, the disconnect is never noticed. It's been done where
a WiFi connection may quit and then re-start. To determine the amount of
time you can have a disconnect, just pull the Internet plug and plug it back
in again to see if you get a state change. If you don't, the disconnect was
never noticed.
HTH,
Bill
On Aug 11, 2005, at 10:43 AM, Graeme Bull wrote:
nope, no built in functionality at all. If the connection goes down, you
have to watch for that and reconnect people up making sure to keep the
state
of your app in mind when you go to reset values etc and reconnect to the
shared objects and streams.
Graeme
-----Original Message-----
From: Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
[mailto:Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org]
Sent: Thursday, August 11, 2005 11:30 PM
To: graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; FlashComm Mailing List
Cc: 'FlashComm Mailing List'; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: RE: [FlashComm] netconnection.onstatus
I read somewhere that netconnection.onstatus has a sort of "built-in"
functionality to reconnect to the server if disconnected. Am I wrong?
I
guess my question is, would "NetConnection.Connect.Success" change to
"NetConnection.Connect.Closed" and then back to
"NetConnection.Connect.Success", in which case everything within would
be
executed again. Or, is it more seamless where a netconnection info
object
isn't really even sent in this case?
Thanks again,
Brandon
"Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 10:03 AM Please respond to
graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To "'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject RE: [FlashComm] netconnection.onstatus
It's not so bad, but it would be better to call a function that does
the
shared object getting just to keep things all seperate. And you never
know
what state your app is in when it is required to "reboot". Which would
mean
making a decision on whether you need to connect up to the SO and what
you
want to do with the data etc..
It really depends on the complexity of your application I suppose.
Graeme
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
Sent: Thursday, August 11, 2005 10:15 PM
To: FlashComm Mailing List
Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] netconnection.onstatus
Might be a dumb question.
I have the following:
client_nc = new NetConnection();
client_nc.onStatus = function(info) {
if (info.code == "NetConnection.Connect.Success") {
so = SharedObject.getRemote("soInfo", client_nc.uri,
true);
so.onSync = function(list) {
//do something
}
}
}
Is it dangerous to put any sort of function inside the
client_nc.onStatus?
If a client is disconnected, and is then automatically reconnected,
will
"NetConnection.Connect.Success" be sent again, thereby initializing
everthing inside the client_nc.onStatus a second time?
Thanks,
Brandon
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+w 2005-08-11, 5:46 pm |
| I have a tracking system setup where logout time is saved to a shared
object onDisconnect. Some of my logs show users disconnecting and
reconnecting at the same exact time, to the second. I assumed that a
disconnect/reconnect thing happened often and is noticed server-side, but
not client-side, making it seamless for the user. Make sense?
Thanks,
Brandon
Bill Sanders <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 10:58 AM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To
graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org, FlashComm Mailing List
<flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject
Re: [FlashComm] netconnection.onstatus
Hi Brandon/Graeme,
I've been doing some work with disconnects and I found that if you
reconnect soon enough, the disconnect is never noticed. It's been
done where a WiFi connection may quit and then re-start. To determine
the amount of time you can have a disconnect, just pull the Internet
plug and plug it back in again to see if you get a state change. If
you don't, the disconnect was never noticed.
HTH,
Bill
On Aug 11, 2005, at 10:43 AM, Graeme Bull wrote:
> nope, no built in functionality at all. If the connection goes
> down, you
> have to watch for that and reconnect people up making sure to keep
> the state
> of your app in mind when you go to reset values etc and reconnect
> to the
> shared objects and streams.
>
> Graeme
> -----Original Message-----
> From: Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
> [mailto:Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org]
> Sent: Thursday, August 11, 2005 11:30 PM
> To: graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; FlashComm Mailing List
> Cc: 'FlashComm Mailing List'; flashcomm-
> bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> Subject: RE: [FlashComm] netconnection.onstatus
>
>
>
> I read somewhere that netconnection.onstatus has a sort of "built-
> in"
> functionality to reconnect to the server if disconnected. Am I
> wrong? I
> guess my question is, would "NetConnection.Connect.Success" change to
> "NetConnection.Connect.Closed" and then back to
> "NetConnection.Connect.Success", in which case everything within
> would be
> executed again. Or, is it more seamless where a netconnection info
> object
> isn't really even sent in this case?
>
> Thanks again,
> Brandon
>
>
>
> "Graeme Bull" <graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org>
> Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> 08/11/2005 10:03 AM Please respond to
> graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org; Please respond to
> FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
>
>
> To "'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
> cc
> Subject RE: [FlashComm] netconnection.onstatus
>
>
>
>
>
>
>
> It's not so bad, but it would be better to call a function that
> does the
> shared object getting just to keep things all seperate. And you
> never know
> what state your app is in when it is required to "reboot". Which
> would
> mean
> making a decision on whether you need to connect up to the SO and
> what you
> want to do with the data etc..
>
> It really depends on the complexity of your application I suppose.
>
> Graeme
>
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org]On Behalf Of
> Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org
> Sent: Thursday, August 11, 2005 10:15 PM
> To: FlashComm Mailing List
> Cc: FlashComm Mailing List; flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> Subject: [FlashComm] netconnection.onstatus
>
>
> Might be a dumb question.
>
> I have the following:
>
> client_nc = new NetConnection();
> client_nc.onStatus = function(info) {
> if (info.code == "NetConnection.Connect.Success") {
> so = SharedObject.getRemote("soInfo", client_nc.uri,
> true);
> so.onSync = function(list) {
> //do something
> }
> }
> }
>
> Is it dangerous to put any sort of function inside the
> client_nc.onStatus?
> If a client is disconnected, and is then automatically
> reconnected, will
> "NetConnection.Connect.Success" be sent again, thereby initializing
> everthing inside the client_nc.onStatus a second time?
>
> Thanks,
> Brandon
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Bill Sanders 2005-08-11, 5:46 pm |
| Hi Brandon,
I never thought of that, but I see what you're saying. The gap is
between the disconnect and the message being received on the SS and
the CS. The SS is getting it right away, and the CS catches it a few
seconds later. I wonder if that's built into FCS or an unintended bug.
Bill
On Aug 11, 2005, at 11:03 AM,
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org wrote:
> I have a tracking system setup where logout time is saved to a shared
> object onDisconnect. Some of my logs show users disconnecting and
> reconnecting at the same exact time, to the second. I assumed that a
> disconnect/reconnect thing happened often and is noticed server-
> side, but
> not client-side, making it seamless for the user. Make sense?
>
> Thanks,
> Brandon
>
>
>
>
> Bill Sanders <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
> Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> 08/11/2005 10:58 AM
> Please respond to
> FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
>
>
> To
> graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org, FlashComm Mailing List
> <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
> cc
>
> Subject
> Re: [FlashComm] netconnection.onstatus
>
>
>
>
>
>
> Hi Brandon/Graeme,
>
> I've been doing some work with disconnects and I found that if you
> reconnect soon enough, the disconnect is never noticed. It's been
> done where a WiFi connection may quit and then re-start. To determine
> the amount of time you can have a disconnect, just pull the Internet
> plug and plug it back in again to see if you get a state change. If
> you don't, the disconnect was never noticed.
>
> HTH,
> Bill
>
> On Aug 11, 2005, at 10:43 AM, Graeme Bull wrote:
>
>
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+w 2005-08-11, 5:46 pm |
| I bet it's unintended, but cool nonetheless.
Thanks
Bill Sanders <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
08/11/2005 11:17 AM
Please respond to
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
To
FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
cc
Subject
Re: [FlashComm] netconnection.onstatus
Hi Brandon,
I never thought of that, but I see what you're saying. The gap is
between the disconnect and the message being received on the SS and
the CS. The SS is getting it right away, and the CS catches it a few
seconds later. I wonder if that's built into FCS or an unintended bug.
Bill
On Aug 11, 2005, at 11:03 AM,
Brandon_Krakowsky-t6Q6IArRIhmxKhIkFyZ7poFTLv+wk40W@public.gmane.org wrote:
> I have a tracking system setup where logout time is saved to a shared
> object onDisconnect. Some of my logs show users disconnecting and
> reconnecting at the same exact time, to the second. I assumed that a
> disconnect/reconnect thing happened often and is noticed server-
> side, but
> not client-side, making it seamless for the user. Make sense?
>
> Thanks,
> Brandon
>
>
>
>
> Bill Sanders <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
> Sent by: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> 08/11/2005 10:58 AM
> Please respond to
> FlashComm Mailing List <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
>
>
> To
> graeme.bull-lB/6vUJvybQOPmVbiNFCMNBPR1lH4CV8@public.gmane.org, FlashComm Mailing List
> <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org>
> cc
>
> Subject
> Re: [FlashComm] netconnection.onstatus
>
>
>
>
>
>
> Hi Brandon/Graeme,
>
> I've been doing some work with disconnects and I found that if you
> reconnect soon enough, the disconnect is never noticed. It's been
> done where a WiFi connection may quit and then re-start. To determine
> the amount of time you can have a disconnect, just pull the Internet
> plug and plug it back in again to see if you get a state change. If
> you don't, the disconnect was never noticed.
>
> HTH,
> Bill
>
> On Aug 11, 2005, at 10:43 AM, Graeme Bull wrote:
>
>
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|
|
|
|
|