On May 26, 2015, at 11:04 , Tomas Jelinek <tjelinek(a)redhat.com> wrote:
we have an interesting bug report from Sandro  which says that after the connection
between engine and moVirt goes down, moVirt does not notify the user about this and keeps
old data in the UI as if nothing happened even they are weeks old. This is obviously not
correct but not exactly clear how should it behave. I see this options:
- if the connection fails during the refresh, set all the statuses of everything to
(I would not do this since this would generate the notifications and may be temporal
(e.g. phone in tunnel or something))
- leave the data as they are and have some top bar or something saying how old the data
are. This would be updated at every poll
(Not sure, would occupy place and would make it hard for partial updates. And track this
for each entity is costy)
- leave the data as they are and if some server communication fails add a top bar with a
warning that the connection to server is lost and the data are old - maybe with some note
when was the last successful connection.
(this seems simple enough and my favorite but still not convinced I like it…)
how about greying out the outdated data a little, after some period?
Any more ideas?
moVirt mailing list