|
Home > Archive > Macromedia Flash Server > August 2006 > nc.close doesn't do jack... sometimes
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 |
nc.close doesn't do jack... sometimes
|
|
| Jorge Maiquez 2006-04-27, 6:48 am |
| Hey guys,
Don't know if anyone has come across this, or if this is a known issue, but
if nc.close() is called from within the onStatus handler (after a
"NetConnection.Connect.Succes"), then it doesn't do anything.
- Create an (empty) FCS/FMS app folder called "TestNcApp".
- Put the following code in a FLA and run it.
<-------------------
import mx.utils.Delegate;
nc = new NetConnection();
nc.onStatus = Delegate.create(this, onNcStatus);
nc.connect("rtmp://localhost/TestNcApp");
function onNcStatus(info:Object){
if(info.code == "NetConnection.Connect.Success"){
trace("Successful connection. Attempting close...");
nc.close();
}
else if(info.code == "NetConnection.Connect.Closed"){
trace("Closed the NetConnection");
}
}
------------------->
You'll not see the trace: "Closed the NetConnection".
Funnily enough, it does work if you put that close call in an interval, as
in the following code:
<-------------------
import mx.utils.Delegate;
nc = new NetConnection();
nc.onStatus = Delegate.create(this, onNcStatus);
nc.connect("rtmp://localhost/TestNcApp");
function onNcStatus(info:Object){
if(info.code == "NetConnection.Connect.Success"){
trace("Successful connection. Attempting close...");
ncIntvl = setInterval(delayClose, 1000);
}
else if(info.code == "NetConnection.Connect.Closed"){
trace("Closed the NetConnection");
}
}
function delayClose(){
trace("Delayed attempt to close the NetConnection");
clearInterval(ncIntvl);
nc.close();
}
------------------->
And it even works if you use a 0 (zero) instead of the 1000!
Go and figure.. 
-Jorge
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-04-27, 6:48 am |
| Could it be a scope issue?
Maybe this works?
import mx.utils.Delegate;
nc = new NetConnection();
nc.onStatus = Delegate.create(this, onNcStatus);
nc.connect("rtmp://localhost/TestNcApp");
function onNcStatus(info:Object){
if(info.code == "NetConnection.Connect.Success"){
trace("Successful connection. Attempting close...");
this.close();
}
else if(info.code == "NetConnection.Connect.Closed"){
trace("Closed the NetConnection");
}
}
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Jorge Maiquez
> Sent: 25 April 2006 18:33
> To: 'FlashComm Mailing List'
> Subject: [FlashComm] nc.close doesn't do jack... sometimes
>
> Hey guys,
>
> Don't know if anyone has come across this, or if this is a
> known issue, but if nc.close() is called from within the
> onStatus handler (after a "NetConnection.Connect.Succes"),
> then it doesn't do anything.
>
>
> - Create an (empty) FCS/FMS app folder called "TestNcApp".
> - Put the following code in a FLA and run it.
>
> <-------------------
>
> import mx.utils.Delegate;
>
> nc = new NetConnection();
> nc.onStatus = Delegate.create(this, onNcStatus);
> nc.connect("rtmp://localhost/TestNcApp");
>
> function onNcStatus(info:Object){
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> nc.close();
> }
> else if(info.code == "NetConnection.Connect.Closed"){
> trace("Closed the NetConnection");
> }
> }
>
> ------------------->
>
> You'll not see the trace: "Closed the NetConnection".
>
> Funnily enough, it does work if you put that close call in an
> interval, as in the following code:
>
>
> <-------------------
>
> import mx.utils.Delegate;
>
> nc = new NetConnection();
> nc.onStatus = Delegate.create(this, onNcStatus);
> nc.connect("rtmp://localhost/TestNcApp");
>
> function onNcStatus(info:Object){
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> ncIntvl = setInterval(delayClose, 1000);
> }
> else if(info.code == "NetConnection.Connect.Closed"){
> trace("Closed the NetConnection");
> }
> }
>
> function delayClose(){
> trace("Delayed attempt to close the NetConnection");
> clearInterval(ncIntvl);
> nc.close();
> }
>
> ------------------->
>
> And it even works if you use a 0 (zero) instead of the 1000!
> Go and figure..
>
>
> -Jorge
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com http://training.figleaf.com
>
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Jorge Maiquez 2006-04-27, 6:48 am |
| Yeah, that's what I thought at first, but it's not. The following trace
shows that the nc is actually being targeted correctly:
...
if(info.code == "NetConnection.Connect.Success"){
trace("Successful connection. Attempting close...");
trace("Targeting nc with uri: "+nc.uri);
nc.close();
}
...
Dare I say the word... bug?
-J
-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
Sent: 25 April 2006 20:49
To: 'FlashComm Mailing List'
Subject: RE: [FlashComm] nc.close doesn't do jack... sometimes
Could it be a scope issue?
Maybe this works?
import mx.utils.Delegate;
nc = new NetConnection();
nc.onStatus = Delegate.create(this, onNcStatus);
nc.connect("rtmp://localhost/TestNcApp");
function onNcStatus(info:Object){
if(info.code == "NetConnection.Connect.Success"){
trace("Successful connection. Attempting close...");
this.close();
}
else if(info.code == "NetConnection.Connect.Closed"){
trace("Closed the NetConnection");
}
}
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Jorge
> Maiquez
> Sent: 25 April 2006 18:33
> To: 'FlashComm Mailing List'
> Subject: [FlashComm] nc.close doesn't do jack... sometimes
>
> Hey guys,
>
> Don't know if anyone has come across this, or if this is a known
> issue, but if nc.close() is called from within the onStatus handler
> (after a "NetConnection.Connect.Succes"), then it doesn't do anything.
>
>
> - Create an (empty) FCS/FMS app folder called "TestNcApp".
> - Put the following code in a FLA and run it.
>
> <-------------------
>
> import mx.utils.Delegate;
>
> nc = new NetConnection();
> nc.onStatus = Delegate.create(this, onNcStatus);
> nc.connect("rtmp://localhost/TestNcApp");
>
> function onNcStatus(info:Object){
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> nc.close();
> }
> else if(info.code == "NetConnection.Connect.Closed"){
> trace("Closed the NetConnection");
> }
> }
>
> ------------------->
>
> You'll not see the trace: "Closed the NetConnection".
>
> Funnily enough, it does work if you put that close call in an
> interval, as in the following code:
>
>
> <-------------------
>
> import mx.utils.Delegate;
>
> nc = new NetConnection();
> nc.onStatus = Delegate.create(this, onNcStatus);
> nc.connect("rtmp://localhost/TestNcApp");
>
> function onNcStatus(info:Object){
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> ncIntvl = setInterval(delayClose, 1000);
> }
> else if(info.code == "NetConnection.Connect.Closed"){
> trace("Closed the NetConnection");
> }
> }
>
> function delayClose(){
> trace("Delayed attempt to close the NetConnection");
> clearInterval(ncIntvl);
> nc.close();
> }
>
> ------------------->
>
> And it even works if you use a 0 (zero) instead of the 1000!
> Go and figure..
>
>
> -Jorge
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Owen van Dijk 2006-08-21, 7:11 am |
| I'm just kicking this old thread alive again, cause it's definitely a
bug ( FMS 2.02 ), i just implemented the workaround described below,
after seeing some really weird 'ghost' connections in the console
where connections where not closed even if there was a call to
nc.close(); we had up to 50% of our connections not being closed and
just sitting idle.
should we log a bug?
On 4/26/06, Jorge Maiquez <j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org> wrote:
> Yeah, that's what I thought at first, but it's not. The following trace
> shows that the nc is actually being targeted correctly:
>
> ..
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> trace("Targeting nc with uri: "+nc.uri);
> nc.close();
> }
> ..
>
> Dare I say the word... bug?
>
> -J
>
>
>
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of Stefan Richter
> Sent: 25 April 2006 20:49
> To: 'FlashComm Mailing List'
> Subject: RE: [FlashComm] nc.close doesn't do jack... sometimes
>
> Could it be a scope issue?
> Maybe this works?
>
>
> import mx.utils.Delegate;
>
> nc = new NetConnection();
> nc.onStatus = Delegate.create(this, onNcStatus);
> nc.connect("rtmp://localhost/TestNcApp");
>
> function onNcStatus(info:Object){
> if(info.code == "NetConnection.Connect.Success"){
> trace("Successful connection. Attempting close...");
> this.close();
> }
> else if(info.code == "NetConnection.Connect.Closed"){
> trace("Closed the NetConnection");
> }
> }
>
>
>
>
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
--
Owen van Dijk
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-08-21, 7:11 am |
| Remnind us again of the workaround. Is it the interval approach?
Stefan
[vbcol=seagreen]
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org] On Behalf Of
> Owen van Dijk
> Sent: 21 August 2006 12:27
> To: FlashComm Mailing List
> Subject: Re: [FlashComm] nc.close doesn't do jack... sometimes
>
> I'm just kicking this old thread alive again, cause it's
> definitely a bug ( FMS 2.02 ), i just implemented the
> workaround described below, after seeing some really weird
> 'ghost' connections in the console where connections where
> not closed even if there was a call to nc.close(); we had up
> to 50% of our connections not being closed and just sitting idle.
>
> should we log a bug?
>
> On 4/26/06, Jorge Maiquez <j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org> wrote:
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Stefan Richter 2006-08-21, 7:11 am |
| Just for the record and in order to eliminate Delegate as a source of the
problem, here's another piece of code which does *not* work as expected:
nc = new NetConnection();
nc.onStatus = function (info:Object)
{
trace(info.code)
if(info.code == "NetConnection.Connect.Success")
{
trace("Successful connection. Attempting close...");
closeNC();
}
else if(info.code == "NetConnection.Connect.Closed")
{
trace("Closed the NetConnection");
}
}
function closeNC()
{
trace("closeNC");
nc.close();
}
nc.connect("rtmp://localhost/TestNcApp");
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Owen van Dijk 2006-08-21, 7:11 am |
| Sorry, yup the delayed netconnection close using an interval:
private function delayedNetConnectionClose(
inConnection:NetConnection ) : Void {
trace("SuperClass.delayedNetConnectionClose(" +
inConnection.isConnected + ")");
inConnection.close();
trace("SuperClass.delayedNetConnectionClose(" +
inConnection.isConnected + ")");
// clear the interval
clearInterval( _delayedNetConnectionCloseID );
};
On 8/21/06, Stefan Richter <stefan-fMeCE+ULXElEfu+5ix1nRw@public.gmane.org> wrote:
> Just for the record and in order to eliminate Delegate as a source of the
> problem, here's another piece of code which does *not* work as expected:
>
> nc = new NetConnection();
>
> nc.onStatus = function (info:Object)
> {
> trace(info.code)
> if(info.code == "NetConnection.Connect.Success")
> {
> trace("Successful connection. Attempting close...");
> closeNC();
> }
> else if(info.code == "NetConnection.Connect.Closed")
> {
> trace("Closed the NetConnection");
> }
> }
>
> function closeNC()
> {
> trace("closeNC");
> nc.close();
> }
>
> nc.connect("rtmp://localhost/TestNcApp");
>
>
>
>
>
>
>
>
>
>
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
--
Owen van Dijk
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Owen van Dijk 2006-08-21, 7:11 am |
| Looks i was too quick...forgot to add the following:
_delayedNetConnectionCloseID = setInterval( this,
"delayedNetConnectionClose", 10, nc );
i think a DoLater approach works as well...as the saying goes: if all
fails, wait 1 frame ;)
On 8/21/06, Owen van Dijk <owen.van.dijk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Sorry, yup the delayed netconnection close using an interval:
>
> private function delayedNetConnectionClose(
> inConnection:NetConnection ) : Void {
> trace("SuperClass.delayedNetConnectionClose(" +
> inConnection.isConnected + ")");
> inConnection.close();
> trace("SuperClass.delayedNetConnectionClose(" +
> inConnection.isConnected + ")");
>
> // clear the interval
> clearInterval( _delayedNetConnectionCloseID );
> };
>
--
Owen van Dijk
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Bill Sanders 2006-08-21, 7:11 am |
| Owen,
I'd log a bug--in fact maybe we all ought to log bugs. Everyone at
Adobe has been suspiciously quiet lately. I wonder what's up. A new FMS?
Bill
On Aug 21, 2006, at 7:27 AM, Owen van Dijk wrote:
> I'm just kicking this old thread alive again, cause it's definitely a
> bug ( FMS 2.02 ), i just implemented the workaround described below,
> after seeing some really weird 'ghost' connections in the console
> where connections where not closed even if there was a call to
> nc.close(); we had up to 50% of our connections not being closed and
> just sitting idle.
>
> should we log a bug?
>
> On 4/26/06, Jorge Maiquez <j_maiquez-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org> wrote:
>
>
> --
> Owen van Dijk
> ________________________________________
_______
> FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
|
| Geachte heer/mevrouw,
Ik ben t/m 25 augustus afwezig. Ik zal uw mail daarna zo snel mogelijk in behandeling nemen. Voor dringende zaken met betrekking tot WEBclusive kunt u ons kantoor bellen op het volgende nummer: 070-3699 817
Met vriendelijke groet,
Wouter van Vliet
WEBclusive
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Owen van Dijk 2006-08-21, 1:12 pm |
| On 8/21/06, Bill Sanders <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org> wrote:
> Owen,
>
> I'd log a bug--in fact maybe we all ought to log bugs. Everyone at
> Adobe has been suspiciously quiet lately. I wonder what's up. A new FMS?
>
> Bill
Is there a public bugbase or emailadres where we can log bugs? It's
actually a flash player related bug ( the netconnection code ), not a
fms bug per se.
I think a new FMS with DRM support is in the making ;)
--
Owen van Dijk
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Dario De Agostini 2006-08-21, 1:12 pm |
| Bill Sanders wrote:
>
> I'd log a bug--in fact maybe we all ought to log bugs. Everyone at
> Adobe has been suspiciously quiet lately. I wonder what's up. A new FMS?
I've been in contact with them because we filled a bug (regarding
license-connection count).
I'd say they have been more active lately than before
They probably quit writing on public lists due to the "panic" it always
created.
btw Owen:
http://www.adobe.com/cfusion/mmform...form&product=16
Dario De Agostini
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
|
|
| Bill Sanders 2006-08-21, 1:12 pm |
| Dario,
I think keeping in contact with the lumpen proletariat has the
opposite effect. People only panic when their imaginations run wild.
Sort of like Hank's humor--never sure when he's being serious. (Well,
Brian understands it, but then again, Brian understands a lot of
things that the rest of us don't.)
However, I'm glad to hear that their customer service is good.
Kindest regards,
Bill
On Aug 21, 2006, at 8:15 AM, Dario De Agostini wrote:
> They probably quit writing on public lists due to the "panic" it
> always created.
bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Dario De Agostini 2006-08-21, 1:12 pm |
| Bill Sanders wrote:
> Dario,
>
> I think keeping in contact with the lumpen proletariat has the
> opposite effect. People only panic when their imaginations run wild.
> Sort of like Hank's humor--never sure when he's being serious. (Well,
> Brian understands it, but then again, Brian understands a lot of
> things that the rest of us don't.)
I completely agree with you.
Especially because a list like this exists!
This list has too many hungry FMS2 fanatics (j/k) which go wild,sometimes.
I'd love to be able to keep in touch with fms2 development to know where
the whole thing is heading... what we can expect from near future or
remote future.
It may save our business.
Let's see if the new "adobe" management will change things. It has not
be a paradise for us, developers, so far.
Dario De Agostini
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Owen van Dijk 2006-08-22, 7:12 am |
| Last post regarding this, the bugline shoud read:
"nc.close() doesn't work if called immediately from the onStatus
handler (in the same frame)"
Now in normal use cases this rarely happens, unless if you follow's
Adobe's guidelines when dealing with firewalls and proxies, outlined
in the article at
http://www.adobe.com/devnet/flashco...ming_print.html
In the article there is a strategy suggested to test different
netconnections on different ports using different protocols. As we
found out on this list, if you call nc.close directly in the onStatus
handler the NetConnection is actually never closed. The workaround is
to delegate the closing 'a frame later' using setTimeout or
setInterval. The bug is present in FP 7, 8 and 9 ( tested on WIN ).
I will post a blogposting later today as well submit a formal
bugreport to Macromedia as i test with different use cases and code
Thanks all!
--
Owen van Dijk
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
| |
| Alexander Farber 2006-08-22, 7:12 am |
| Hello,
On 8/22/06, Owen van Dijk <owen.van.dijk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
http://www.adobe.com/devnet/flashco...ming_print.html
>
> In the article there is a strategy suggested to test different
> netconnections on different ports using different protocols.
sorry if I say smth. stupid - I am a Flash/FMS-newbie,
but I wonder about the 2nd line here (from the above article):
private var k_DEFAULTCONNLIST = [
{protocol:"rtmp", port:1935},
{protocol:"rtmp", port:443},
{protocol:"rtmpt", port:80}
];
Is rtmp supposed to work over the web-proxy, port 443 at all?
And if there is no web-proxy inbetween, then there is no point
for trying rtmp @ port 443, because the 1st line will work.
So IMHO it should be "rtmpt" or "rtmps", like here:
private var k_DEFAULTCONNLIST = [
{protocol:"rtmp", port:1935},
{protocol:"rtmpt", port:443},
{protocol:"rtmpt", port:80}
];
Regards
Alex
--
http://preferans.de
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
|
|
|
|
|