[MDSAL-844] Disconnect (DOM)DataTreeIdentifier from serialization Created: 09/Dec/23 Updated: 10/Dec/23 Resolved: 10/Dec/23 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding API, DOM API |
| Affects Version/s: | None |
| Fix Version/s: | 13.0.0 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||
| Sub-Tasks: |
|
||||||||||
| Epic Link: | NMDA support | ||||||||||
| Description |
|
Both Binding DataTreeIdentifier and DOMDataTreeIdentifier are used to address datastore content. We would be hard-pressed to come up with better names, so for NMDA evolution we really need to start thinking about how to repurpose them. Since both are HierarchicalIdentifiers, they are are also serializable and they do not have serialization proxies. We need to switch them to use serialization proxies, so they can be evolved. The flip side of that is that we will also have more efficient serialization. |