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

Reply via email to