AMF and pure TCP

[dandruph]

Hi everyone,

I'm writing a real-time web front-end that will occasionally need to
send and receive lots of low-latency traffic. My current system is
written in Flash and uses raw TCP sockets, which are nice and
lightweight but not very user-friendly. I'm thinking of switching over
from a home-brew protocol to AMF, but almost all the examples I see
(both here and at PyAMF) are written using TCP over HTTP rather than
raw TCP sockets.

Does anyone use raw TCP sockets? Are the performance gains just not
worth it vs. HTTP? My system may need to send small (<50byte) packets
at a frequency up to 1/~50ms, so header size is actually important for
my case. Are things like NetConnection and RPCs only available over
HTTP?

[limscoder]

NetConnection operates over HTTP. You can still use AmFast to
serialize data going across your socket, you will just need to use the
encoder/decoder classes directly instead of having the framework
automatically encode/decode AMF message packets.

-Dave