[sr-dev] Renaming a module

Carlos Ruiz Díaz carlos.ruizdiaz at gmail.com
Fri Mar 21 17:29:55 CET 2014


My vote for the renaming. It is very confusing to have mediaproxy-ng +
rtpproxy | rtpproxy-ng modules, when you also have mediaproxy module and
rtpproxy-proxy and mediaproxy-proxy, IYKWIM.

Regards,


On Fri, Mar 21, 2014 at 10:15 AM, Juha Heinanen <jh at tutpro.com> wrote:

> Richard Fuchs writes:
>
> > We're slowly getting ready for a new major release of mediaproxy-ng
> > (3.x), which will include some exciting new features, most importantly
> > much improved support for WebRTC. To support those features, rtpproxy-ng
> > needs to support additional flags for the offer/answer functions.
>
> This is great news.  In my opinion it would be better to rename
> rtpproxy-ng module rather than leave its existing version hanging there,
> because I'm sure that current users of the module will migrate to the
> new one anyhow.
>
> -- Juha
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>



-- 
Carlos
http://caruizdiaz.com
http://ngvoice.com
+595981146623
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20140321/f66c6f3d/attachment.html>


More information about the sr-dev mailing list