With API v3 in the works for TC 5.0, should we take this opportunity to do
2 things:

1. rename xmppId to hashId as that appears to be its real use as the hash
id that traffic router uses in its consistent hashing algorithm.

(actually, xmppId is currently used as the hash id IF it exists else
hostname is used which can result in duplicate hash ids -
https://github.com/apache/trafficcontrol/issues/2156)

2. delete xmppPasswd as it appears to have no use.

This PR is a step in the right direction, but wondering if we can go
farther - https://github.com/apache/trafficcontrol/pull/4881

Jeremy

Reply via email to