View Issue Details

IDProjectCategoryView StatusLast Update
001047810000-017: Alias NamesSpecpublic2025-11-11 17:08
ReporterPaul Hunkar Assigned ToPaul Hunkar  
PrioritynormalSeverityfeatureReproducibilityalways
Status assignedResolutionopen 
Target Version1.05 
Summary0010478: Improve aliasname handling of on-line changes
Description

For a GDS or Aggregating server, it is difficult to detect changes in a server when an Aliasname is added or changed.
Servers that support AliasName should be able to indicate changes in a better manner than modelchange events - which requires a subscription / connection to the server.

Additional Information

a proposal is to have a multi-cast or other PubSub notification of model changes. Than any GDS or aggregating can listen for changes and detect if something changes.

further more even a client that is interested in AliasName (for resolution) could also listen and detect if a new AliasName comes on-line (i.e. even the Aggregating server can send notifications to a multicxst address.

TagsNo tags attached.
Commit Version1.05.07 RC1
Fix Due Date

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2025-08-20 15:50 Paul Hunkar New Issue
2025-08-20 15:50 Paul Hunkar Status new => assigned
2025-08-20 15:50 Paul Hunkar Assigned To => Paul Hunkar
2025-11-11 17:08 Jim Luth Commit Version => 1.05.07 RC1