Bob Ippolito wrote:
> On 8/21/06, Alex Thurlow <[EMAIL PROTECTED]> wrote:
>
>>
>
> Using RTMP instead of HTTP is definitely going to make it
> significantly harder to capture the data, but only because there
> aren't yet readily available tools to do it. If some RTMP based
> service becomes popular enough then someone will write the tool to
> make it simple to save FLV streams out of an RTMP connection. Such a
> tool might be developed anyway for Red5 development as a debugging
> tool.
<snip>
>
> Chances are you'll spend weeks of your time trying to implement
> (fundamentally flawed) countermeasures that will probably be broken
> with less effort than you spent constructing them.
>
> -bob
>
Thanks for the info. That's about what I was thinking. Now, the other
(and actually more important) thing I want to prevent is deep-linking.
That is, I don't want anyone else linking to our streams without going
to the site or playing the ad beforehand. I have code for one time http
links, and I was hoping to adapt that to rtmp links. Basically, the
user is linked to by a page that generates a unique ID and writes it to
a file. The rtmp link then has that ID in it. When it is visted a set
number of times ( between 1 and 5 I think), it is removed from the file
and is no longer a valid link. I am wondering if anyone sees any
problems with this method or has already implemented something of the
sort.
Thanks,
Alex Thurlow
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
