Expand my Community achievements bar.

HTTP, RTMP and AMF Question

Avatar

Level 2
From the standpoint of FDS, can I use ANY of these three
protocols (RTMP, HTTP, AMF-with-polling) to get the same
functionality? The documentation seems to indicate that if I use
RTMP, I might have issues with firewalls AND I will find that when
a user refreshes the browser, that the application reloads and a
new session is created. Can I just switch over to HTTP or AMF with
Polling and get all the same benefits without having to worry about
firewalls and browser reloads? If I use HTTP or AMF+Polling, will I
get the nice automatic client update feature where User X makes a
data update and User Y's screen automatically reflects the changes?
I was thinking I might just add HTTP and/or AMP-Polling to the list
of channels in my Destination XML tag and avoid any of the
reloading/firewall issues. Comments?
3 Replies

Avatar

Level 3
Using rtmp or polling channel should give you same
functionality. However, rtmp push data to client when update
arrives. It doesn't have to reconnect to the server. It should
perform better.

Avatar

Level 2
Does HTTP offer a polling option? Or is there a way to use
RTMP in such a way that a browser refresh won't clear the
session?

Avatar

Level 3
HttpChannel has polling too. Refresh a browser is same as
restarting the application. For the live connection, it has to
close and reopen. It has to be a new session