Quote:
Originally Posted by blood.eaglz
#2 what I would like is for all 3 to use a SINGLE rmtpdump exe rather than have to have a separate one for all 3, if it wasn't for the possibility of one or two being incompatible with a newer version I would suggest they simply looked for rtmpdump.exe
|
Well, that would be possible of course. In effect, I use just rtmpdump v2.3 - for p7 it is renamed as rtmpdump v2.2c (not its exact name, but you get the idea), for SBS it is called rtmpdump v2.2d.
I have confidence that v2.3 works OK for all 3 nappers.
With user settings, the programmer allows some flexibility to change, over time. The exact name and location of the rtmpdump file to be used is stored in a settings file. Its location can be secured so that inexperiened users don't kill the settings, or change them to make the application unuseable. I can understand why
mce might be reluctant to take this approach, but it can be made foolproof.
If all 3 nappers expected to see rtmpdump.exe in the working folder (ie, there is none of the win32-2.2c stuff in the filename), then as a new rtmpdump is released and recommended, you would download it (for arguments' sake, let us say it is v2.3a) and name it as rtmpdump.exe, replacing the older file (which might actually be v2.2c).
Is this more than obvious?