[hyc]

Originally Posted by placebo

Let's summarize (and correct me if i am wrong):

• rtmpdump.exe is for Windows. and it works.
• rtmpsrv.exe is for Windows and works too. it facilitates the secure use of rtmpdump.exe.

The purpose of the rtmpsrv program is to intercept a connection from an RTMP client and extract its connection parameters so that they can be passed to rtmpdump. The intent is to provide an automated way to discover the parameters, which would otherwise have to be tediously extracted from various HTML, XML, or SWF files scattered across a web site. There's nothing that makes it any more or less secure.

• rtmpsuck could be used on Windows but no Windows user uses it (because they dont need it or because they dont want to buy your software. like me. i am not going to buy your software, no thanks.). it primarily aims at Linux users.

rtmpsuck was written for Linux, which has a complete TCP/IP networking stack that isn't brain-damaged by design. It relies on networking features that are generally present by default on any Linux machine. Its purpose is similar to rtmpsrv's - it intercepts an outgoing RTMP session. But instead of just collecting parameters that can later be used with rtmpdump, it runs in a passthru mode so that it can just save the data while the client is running. The main reason rtmpsuck is useful is because it should work regardless of whatever silly security token methods might be in use on a client or server. Since it just operates in passthru mode, it doesn't need to understand what those security methods are, it just has to pass them thru faithfully.

rtmpsuck can be made to work on Windows, if you add some 3rd party software to extend the TCP/IP stack to support connection redirection. There are many 3rd party products that can add this feature. I only commented that I am not aware of any free ones. I never implied that my company's was the only option.

And as already noted - NO, IF YOU'RE ON WINDOWS YOU REALLY DON'T NEED ANY OF THIS. Please go and use GetFLV or StreamTransport or Jaksta or whatever else.

• the documentation of the rtmpdump-package s*cks (otherwise there wouldnt be any need to dedicate a whole forum section to the use of rtmpdump!). it is not a manual per se and does not compare at all to commercially written documentation (or manuals!) of successful commercial software. but this is quite natural or common: documentation of freeware usually lacks or s*cks. and it is even truer for freeware/documentation produced by non-English native speakers.

Well, professionally written documentation comes from professional documentation writers. This is an open source project, anyone is welcome to participate. I am a professional software engineer and I donate my coding skills. Any professional doc writer who wishes to donate their doc writing skills is welcome to participate in the project.