Stream live video - use http or rtmp protocols from player code?

A:

2.  You don't need to copy main.asc unless you have logic in there that you want on your new application.  It's a text file so you can open and read it, get familiar.  allowedDomains is up to your security policy, but if you want it to apply to that application then yes.  Finally the Application.xml in there is an override of the default one in the server's conf directory - so you only need to include it if you plan on overriding settings from the default.

3.  Chosing which type dictates whether or not you're doing HTTP (not streaming) or RTMP (streaming) however you've added a complication that you're only allowed to use port 80 - which RTMP does not by default.  FMLE doesn't support HTTP push to FMS, so the FMS URI must be fomr form of RTMP* so you're left with some good choices

1. Use RTMP over port 80 like so rtmp://myServerName:80/appName/ <- notice the coded port number
2. Use RTMPT which automatically uses port 80 and will get around most proxies that demand HTTP traffic - however there's more performance overhead than RTMP (think maybe 25% more overhead for a wild guess on my part)

I dunno the answer for your FLVPlayback component but I'm going to take a guess that the issue is about the same here and you should use the same parameter that you're using for your RTMP ingest.  At worst I'm pretty sure that it will work and that's not so bad.

Asa