2010-03-31, 02:14
spicemuseum Wrote:I suspect what Jackanddougal means is that a switchable SWFVerify property is largely redundant since it could be assumed to be always necessary...
If you assume swf verification is always a possibility in any stream, then if you receive a request for verification for the stream, you send the response, if you don't, you don't.
WRT the revisions, I don't see anything between those two revision numbers which would make any difference to this.
Certainly; even if you turn on the swfverify option, it will only be used upon request from the server. But the reason not to always generate the hash information by default is that sometimes this has a significant cost in execution time. I.e., you have to fetch the SWF using http, decompress it, and then calculate the hash. It's better not to go through all of that hassle if you know the server won't request it. (Even though all of this hassle is hidden inside librtmp, so it's no big deal to activate it, it still can mean a noticeable delay before a stream can actually be opened and processed.)
