|
Home > Archive > Macromedia Flash Server > June 2006 > 'Dropped' connections in Edge-Origin setup / FPAD
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 |
'Dropped' connections in Edge-Origin setup / FPAD
|
|
| Owen van Dijk 2006-06-10, 7:11 pm |
| Hi All,
Yesterday we setup configured an Edge/Origin solution for
Fabchannel.com and in our testing we found out randomly dropped
NetStreams and/or NetConnections. I'm on a tight deadline as well,
since monday we'll have some major exposure through the Webby Awards
ceremony (we won a Webby award in category 'music'  )) )
We have setup the edges as implicit proxies in our setup and we rely
on the origin to redirect traffic ( through the fpad mechanism ) but
found out that sometimes stream don't start. I have trouble
pinpointing the real problem. I currently looking at endless lines of
both ethereal and fms server logs to see if something odd happens but
nothing yet.
Questions are:
- Anyone have some more technical details on the fpad udp request on
port 67. We see the flash player sending these, but don't receive any
respons? Is fpad implementation based on wpad or is it something
undocumentated? Any technical engineer from Adobe?
- Anyone with similar edge/origin setups experienced the same (
browsing through different streams don't work ).
On a note, we work with quite large streams ( usually over an hour in
length and 800-1000MB in size ). You'll need FMS 2 Updater1 to to
actually be able to handle such large stream correctly.
I'll crosspost this mail to the Adobe FMS forums too, so sorry if you
see this message twice.
--
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
| |
| Patrick Simon 2006-06-12, 1:11 pm |
| Hi Owen,
I'll help you offline with your second question to fix your
configuration and/or application.=20
But let me get back on the first question, because it may be of interest
for the list as well.
It's okay that you're seeing these FPAD messages. Flash Player 8
broadcasts them by default when you call nc.connect(). Saying this, if
you have not configured FPAD on the server, they're not doing any harm.
However, a best practice is to switch them off with nc.fpadZone =3D -1
before you establish the connection with nc.connect();
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
var nc:NetConnection =3D new NetConnection();
nc.fpadZone =3D -1;=20
// the default is 0, to switch FPAD broadcasts off use -1
// then connect by=20
nc.connect();=20
// and you shouldn't see the fpad traffic in
// ethereal (or similar network scanners) anymore.
/*
other fpad settings that are available:
nc.fpadWait =3D 250; // in milliseconds
nc.fpadOnly =3D false; // boolean
nc.fpadPort =3D 67; // Target port to broadcast
nc.fpadInfo.ip =3D edgeip; // only available if proxy is detected
nc.fpadInfo.port =3D edgeport; // only available if proxy is detected.
The default behaviour is that the player broadcasts the FPAD message to
port 67 to the network with fpadZone=3D0. Change these before you call
nc.connect()
fpadZone =3D -1 disables this broadcasting mechanism. So if this isn't
required, it must be set to '-1' before call connection.
fpadOnly=3Dtrue will only detect the proxy on the network and won't
connect to the server.
The fpadInfo object is available only when player detects the proxy on
the network. You can trace it in you function for the onStatus event
whether or not the proxy is available.=20
The Player then reconstructs the URL based on the value fpadInfo.ip and
fpadInfo.port. =20
If, for example, there is a poorly configured FMS, this information may
tell you why the connection is not working.
=20
fpadPort can be changed to some other port if the target FMS proxies are
listening on different port other than 67.
fpadWait is timeout for detection. If the player doesn't get a response
back within this timeout from any FMS server on the network, it will
connect to FMS directly with the information you provide with
nc.connect(). For example, even if there is a FMS server available but
it is too slow to respond, the player still has a chance to connect
directly to the FMS Origin server.
*/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
I hope this helps!
Best regards,
Patrick
-----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: Saturday, June 10, 2006 8:31 PM
To: flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
Subject: [FlashComm] 'Dropped' connections in Edge-Origin setup / FPAD
Hi All,
Yesterday we setup configured an Edge/Origin solution for
Fabchannel.com and in our testing we found out randomly dropped
NetStreams and/or NetConnections. I'm on a tight deadline as well,
since monday we'll have some major exposure through the Webby Awards
ceremony (we won a Webby award in category 'music' )) )
We have setup the edges as implicit proxies in our setup and we rely
on the origin to redirect traffic ( through the fpad mechanism ) but
found out that sometimes stream don't start. I have trouble
pinpointing the real problem. I currently looking at endless lines of
both ethereal and fms server logs to see if something odd happens but
nothing yet.
Questions are:
- Anyone have some more technical details on the fpad udp request on
port 67. We see the flash player sending these, but don't receive any
respons? Is fpad implementation based on wpad or is it something
undocumentated? Any technical engineer from Adobe?
- Anyone with similar edge/origin setups experienced the same (
browsing through different streams don't work ).
On a note, we work with quite large streams ( usually over an hour in
length and 800-1000MB in size ). You'll need FMS 2 Updater1 to to
actually be able to handle such large stream correctly.
I'll crosspost this mail to the Adobe FMS forums too, so sorry if you
see this message twice.
--=20
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
________________________________________
_______
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
| |
|
|
|
|
|