I have a typical n-tier application with Data/Domain/UI layers. The domain objects initialise themselves from the DataLayer, but also contain additional state properties that get updated on a 2-second timer. These properties are not written to the DataLayer.
This design requires that the domain objects persist for the life of the application. This is causing problems with data binding to the UI as the domain objects out-live the various UI displays.
I understand the norm is to "new up" a domain object, display it to the UI and then dispose of it. However, my state properties are stopping me from doing this as these would be lost on dispose. I don't really want to store my 2-second state data to the database. What are my options?
Am I attacking this problem from a fundamentally flawed perspective?
Edit 1:
For instance, My Domain object includes a "Live Reading" property which it picks up from an external process every 2 seconds. My UI Layer binds to this property to display this, continually updating, value.