Skip navigation
Deboschere
Currently Being Moderated

StreamingAMFEndpoint and Firewalls

Mar 10, 2010 5:42 AM

Hi.

 

I need to push some data to flex clients.

 

So I put in place the StreamingAMFEndpoint and cie.

 

It works pretty well in a "Standrard" environnement when you have no firewall between the balzeds server and the flex client.

 

But when a firewall is present, the dedicated connection between blazeDsServer and FlexClient isn't established.

 

In the service-config.xml  I have this :

 

<channel-definition id="my-streaming-amf"
            class="mx.messaging.channels.StreamingAMFChannel">
            <endpoint
                url="http://{server.name}:{server.port}/messagebroker/streamingamf"
                class="flex.messaging.endpoints.StreamingAMFEndpoint" />
               
               <properties>
                   <idle-timeout-minutes>0</idle-timeout-minutes>
                   <max-streaming-clients>100</max-streaming-clients>
                   <server-to-client-heartbeat-millis>5000</server-to-client-heartbeat-m illis>
                   <user-agent-settings>
                       <user-agent match-on="MSIE" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
                       <user-agent match-on="Firefox" kickstart-bytes="2048" max-streaming-connections-per-session="3"/>
                   </user-agent-settings>
               </properties>
               
</channel-definition>

 

The fact is the client ask for a connection on the server.port but it then establish the connection on another port let say 4334 for the example.

 

So I suppose it's like with a ftp connection with a range of port dedicated to manage this connections and i have to open ports on my firewall.

 

So here's my Questions :

 

Is there a way to specify this range of ports ?

 

Or is there a port range by default ?

 

 

Regards.

 

Tony

 
Replies
  • Currently Being Moderated
    Mar 14, 2010 10:59 PM   in reply to Deboschere

    I think opening just one port should be enough. When serving standard HTTP traffic, you only need to have port 80 open, even that internally the server might create additional sockets for each client.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points