[FFmpeg-devel] [GSoC] FFserver further development direction

Helmut K. C. Tessarek tessarek at evermeet.cx
Wed Apr 25 03:24:41 EEST 2018


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I'm not an ffmpeg developer, but I do have experience in software
engineering and ddesign.

On 2018-04-24 17:33, Stephan Holljes wrote:
> This arose partly out of the discussion that there is no way to get
> a connected peer's address through the public API (as the
> filedescriptor is hidden in private structs).

How about adding this to the public API then?

> Most people (including my mentor) spoke out in favor of utilizing
> nginx.

This makes no sense at all. So now people who are using Apache are
supposed to use nginx to get a working ffserver implementation?

- -- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAlrfysgACgkQvgmFNJ1E
3QD99w//QVEGlbMgYPoFEkno/Qxcc3tgem4lAzBE6N7bp9SXZBGan1zbsQRA8FN9
0RSHVoiA99M5INIMsagXKym+evWqMFtKpJdQtiV7U30pY+s3WNZBFcYZMFej9fjz
pcyiD34AjkZCLxCY4QjucW7GxKLVyY0QrWfdE5D9T7go21+CfuqWIn4U7aswojVo
Ram7TYLAUb7ZngsgGIUM6Sm6fFyGUISdltaCd9Od2m0sPUH3d488ZN21xZ+nO6Xo
VCiWzYAhEX87AgeYRkNKz5SbYGkGj+TQXupVqmYdvUrJ6BMxC/5bo+PTVaC1hkZa
bGN50cosNUO85Es7eZQraqIY5u19UzHMJJfMkBDnUxmJ21EaF3Xd0dj5xXEJ9Etb
qZiqfvzxbphbvny1yczqTbxyC5noHprXI4UKUfN4w8MfYggBbb5GSbAHyE+G6yUU
dfrV17z3bxGOCH4mxJAQUzNwDTW2LMV1eyA2TuopsCDkHkL6WAbgLepfb4ixtdpK
JA1pDyP2pfWsDSqR1tJ4bpW/72WoMT3ZL8M++947SuBlg9Wyit5y0m9klAnp9cPC
M7415FcCgG3Zl/fVx/SqDsliWCcipqxGnmCMboAKkpAh4WPJG8OEqTohE7uK4EiZ
ac28TsjJ2GT+B1t2IZVk0mtgtPcksOpXW3/bQHjZiI/Bid+a2y8=
=3val
-----END PGP SIGNATURE-----


More information about the ffmpeg-devel mailing list