Timeline for WPF application architecture
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 9, 2018 at 14:05 | vote | accept | DrLazer | ||
| Apr 21, 2017 at 18:19 | comment | added | RubberDuck | That's interesting @PeterM I've done something similar and 100ms does seem to be the sweet spot for updating the screen in real time scenarios. We should trade stories sometimes. | |
| Apr 21, 2017 at 17:14 | comment | added | Peter M | @RubberDuck It depends on the type of application. I have written WPF desktop applications that interface to industrial hardware and updates at sub-second intervals (300ms is a good sweet spot for this. And right now I testing some hardware and trying to push updates to sub 100ms - but it gets messy under about 30ms). But your comment implies web based system and I can see nothing in the OPs question that implies that. | |
| Apr 21, 2017 at 12:00 | history | edited | Gary.Taylor717 | CC BY-SA 3.0 |
deleted 1 character in body
|
| Apr 21, 2017 at 2:00 | comment | added | Gary.Taylor717 | @RubberDuck very true. | |
| Apr 21, 2017 at 1:59 | comment | added | RubberDuck | I would also question whether you really need to update every second, or if every 5 or 10 would suffice. Or even if a publish/subscribe tech, like SignalR, would be better. | |
| Apr 20, 2017 at 16:00 | history | answered | Gary.Taylor717 | CC BY-SA 3.0 |