You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2019/11/25 18:11:19 UTC
[GitHub] [trafficcontrol] alficles commented on issue #4145: Add TO API
Routing Blacklist via cdn.conf
alficles commented on issue #4145: Add TO API Routing Blacklist via cdn.conf
URL: https://github.com/apache/trafficcontrol/pull/4145#issuecomment-558274880
> It just seems like wasted work
Well, the whole endeavor is kinda a short term patch. But I think that "short term" means "at least a year" here. So it's worth at least a little to consider the ops costs folks will incur over the year. Also, I'm a bit concerned about the opportunity for merge conflicts. Any time you create a registry of ids, you're going to get conflicts, especially at the rate we're developing in this area.
> What if every Route had a "Route ID" that was an arbitrary string
I really like this suggestion. It also solves the merge conflict issue.
> what would you name the 10 different variations of the `federations` endpoints
The name is mostly arbitrary. I'd do something fairly regular, though, like:
get-federations
post-federations
delete-federations
put-federations
get-federations-deliveryservices
post-federations-deliveryservices
delete-federations-deliveryservices
... and so on.
A route-name like that would also be handy for recording which handler was invoked for logging purposes if we wanted later.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services