Timeline for OOD vs MVC; Live Objects vs Everything in Database
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 14, 2020 at 23:41 | comment | added | Kain0_0 | I would imagine that you would persist them in the database like you do with the cameras. But just because they are persisted there does not mean you have to operate on them there. You can bulk load them into your application, or dynamically load them on demand. Your application can then performing the timing, event switching, etc... as per its business logic, and in the programming language/environment of your choice/that you've been directed to use. No need to rely on the database as anything other than a handy, queryable serialisation format. | |
| Jun 14, 2020 at 2:23 | comment | added | Daniel Gordon | The database is for persistency. But I don't want to implement in database periodic timer, or events. So I store each ip camera in database with it's ip address. But where do I put my periodic timer and logic? And where do I put the events, and the subscribers to those events? | |
| Jun 10, 2020 at 4:45 | history | answered | Kain0_0 | CC BY-SA 4.0 |