On Mon, 02. Mar 11:41, Anton Khirnov wrote: > Quoting Marton Balint (2020-02-29 17:09:58) > > > > > > On Sat, 29 Feb 2020, Paul B Mahol wrote: > > > > > I think this was already rejected? > > > > jb questioned if this belongs to libavformat, and timo asked how well the > > message brokers handle high bitrates/big message sizes, no hard rejects > > were made as far as I remember. > > > > Andriy provided numbers for scaling, I have not answered the concerns > > regarding libavformat integration, because I am not sure I understand the > > concern. AMQP is a general purpose protocol for message transfer, it even > > has an official URL scheme, so when we integrate it into libavformat as a > > *protocol* I don't really see why it would not fit into the framework or > > what can be gained if it is implemented separately. > > > > If people still have hard feelings against merging this, please speak up, > > but I honestly don't see a problem with it.
> > I would say the question is what is it for? Is anyone using (or > intending to use) this for multimedia transfer? What are the advantages > of doing that over other existing protocols? "why not" does not seem > like a sufficient argument to me. We have 5-10 nodes that are already talking to each other via a RabbitMQ broker. A few of these nodes may be publishing low bitrate multimedia content, and new ones may join the network. The idea is to re-use the RabbitMQ broker instead of using a separate video server, where we can view all the logs (queue sizes, etc.) on the same webui. Also Marton mentioned a use case here: http://ffmpeg.org/pipermail/ffmpeg-devel/2020-February/256976.html -- Andriy _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".