View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010478 | 10000-017: Alias Names | Spec | public | 2025-08-20 15:50 | 2025-11-11 17:08 |
| Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Target Version | 1.05 | ||||
| Summary | 0010478: 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. | ||||
| 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. | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.07 RC1 | ||||
| Fix Due Date | |||||
| 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 |