You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@trafficcontrol.apache.org by Lavanya Bathina <la...@gmail.com> on 2019/11/12 15:53:18 UTC

Re: Traffic Ops Route Deprecation Strategy

+1 on do not rewrite a deprecate route to GO! 

On Nov 12, 2019, at 8:43 AM, Hoppal, Michael <Mi...@comcast.com> wrote:

As the Traffic Ops API is being rewritten from Perl to Golang there has been several routes that have been deprecated and probably more to come.

In the deprecation efforts I have seen two strategies:


 *   The route IS NOT rewritten from Perl to Golang and a deprecation notice is added to the alert response in the Perl handler
 *   The route IS rewritten from Perl to Golang and a deprecation notice is added to the alert response in the Golang handler

I think we should have consistency in our approach and wanted to get people’s thoughts.

I would vote that we do not rewrite a deprecated route from Perl to Golang.

Thanks,

Michael