Francesco Romani wrote: > > In order to make things clear, let me explain what I mean with 'ffmpeg' > module: > while import_mplayer uses an external binary (mplayer!) to do it's work, > import_ffmpeg uses ffmpeg libraries (libavcodec/libaformat/libavutil) and not > depends from any external program. > > In other words, import_mplayer uses mplayer program, but > import_ffmpeg DOES NOT uses ffmpeg program :)
Yes, I understood that. I don't have the same prejudice against the spawning of external programs that you do, I see it as an advantage, since it reduces the maintenance responsibilities of any individual coder. It is often quoted as one of the core benefits of The UNIX Way that program IO should be designed to be passed amongst and between processes. This model has the added benefit of being naturally multi-threaded and capable of making efficient use of multiple cpu's and network connected machines. My own preference is for socket communication, in preference to pipes, fifos, and monolithic programs.
