Skip to content
This repository was archived by the owner on Nov 17, 2020. It is now read-only.

Display user-provided connection name, if any #172

Merged
merged 4 commits into from
Apr 17, 2016

Conversation

hairyhum
Copy link
Contributor

@hairyhum hairyhum commented Apr 6, 2016

If client provided client property connection_name, it will be displayed in management GUI.

Part of rabbitmq/rabbitmq-server#104.

@michaelklishin
Copy link
Contributor

@hairyhum we should not completely replace the name we have. For several reasons:

  • TCP tuple-based ID are used to close connections or get more specific information on them. We absolutely cannot break this for existing systems.
  • User-provided names are not guaranteed to be unique. TCP tuple-based names are (per node).
  • Report unused memory in different color. #500 still uses TCP tuple-based names heavily.

So the user-provided name, when present, should be listed in a separate column (and on the connection page), not replace the name we have.

@michaelklishin michaelklishin self-assigned this Apr 6, 2016
@michaelklishin michaelklishin added this to the n/a milestone Apr 6, 2016
@michaelklishin michaelklishin changed the title Show connection name client property as connection name Display user-provided connection name, if any Apr 17, 2016
To avoid the confusion, don't display client-provided connection
name on the first line.

To avoid very long page titles, move client-provided connection
name into the details section.
@michaelklishin michaelklishin merged commit bfb1347 into stable Apr 17, 2016
@dumbbell dumbbell deleted the rabbitmq-server-104 branch January 3, 2018 08:57
brerx added a commit to brerx/bunny that referenced this pull request Sep 11, 2020
brerx added a commit to brerx/bunny that referenced this pull request Sep 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants