A cursory CPAN search for RTMP yielded a small number of results,
and this Wikipedia article explains that the protocol was released by
Adobe but that the documentation is incomplete:
https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol
"Real-Time Messaging Protocol (RTMP) was initially a
proprietary
protocol developed by Macromedia for streaming audio, video and data
over the Internet, between a Flash player and a server. Macromedia
is now owned by Adobe, which has released an incomplete version of
the specification of the protocol for public use."
Without proper documentation, implementation could be a lot more
difficult (albeit also educational), and might even require some
reverse-engineering (which typically runs the risk of overlooking
subtleties or missing important features).
If you're using TCP, then you should be able to implement this with
ModPerl, but if you're using UDP (which, as I understand, is
generally preferred for these types of protocols) then you'll
probably be better off with a specialist daemon (VideoLAN/VLC my be
able to do this) to serve this in a more direct and efficient way.
Of course, the advantage of using ModPerl for this is that you can
implement specifically customized user-centric access control.
As far as I know, Apache HTTPd doesn't have any options for
listening for UDP packets, and the history in this likely involves
the fact that HTTP was designed with only TCP in mind. While ModPerl
can cetainly be used to implement different protocols (I've done this
before, and I recall once seeing an implementation of an SMTP server
written in Perl that takes advantage of this capability of ModPerl),
these protocols will most likely all need to be TCP-based.
> Hi
>
> on 2019/8/21 0:13, Randolf Richardson wrote:
> > Which streaming protocol(s) do you need to implement?
>
> we use RTMP.
>
> regards.
Randolf Richardson - rand...@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Beautiful British Columbia, Canada
https://www.inter-corporate.com/
