Ticket #563 (closed planned: done)
define track-ID
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | lesser | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | QA cleanup |
| Cc: | Blocked By: | ||
| Blocking: | #155, #516, #692 |
Description
Clarify the role of the trackID, then settle down on a solution how to represent it
- textual ID
- constant defined through facts (config rules)
- relation to the track asset, maybe use this
Change History
Note: See
TracTickets for help on using
tickets.

I've now convinced myself that it's best to use a textual ID, but combined with a hash value. Prototypical implementation is in place. Now the next step would be to throw out asset::Track throughout the code base