<HTML><BODY>agreed<br><br>Понедельник, 1 июня 2015, 3:57 -04:00 от Tomas Jelinek <tjelinek@redhat.com>:<br>
<blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<base target="_self" href="https://e.mail.ru/">
<div id="style_14331454880000000392_BODY"><br>
<br>
----- Original Message -----<br>
> From: "Tomas Jelinek" <<a href="/compose?To=tjelinek@redhat.com">tjelinek@redhat.com</a>><br>
> To: <a href="/compose?To=movirt@ovirt.org">movirt@ovirt.org</a><br>
> Sent: Monday, June 1, 2015 9:33:14 AM<br>
> Subject: Re: [moVirt] when connection fails, user does not know the data are old<br>
> <br>
> Hey,<br>
> <br>
> top posting for conclude:<br>
> - have in the DB a field which will mark that the last connection failed and<br>
> reason or that it succeeded<br>
> - all the screens will have a small top bar showing only when the last call<br>
> failed. It will tell that the connection is lost and that the data are old<br>
<br>
we could also show the last successful poll, but not sure it will not occupy too much place. We can try how will it look like.<br>
<br>
> - fire a notification when you loose the connection - only first time.<br>
> Ideally make this configurable because you not always want this<br>
> - if the connection is lost, the data should be somehow grey and the actions<br>
> should be disabled<br>
> <br>
> This should be 4 different tasks since they bring value one by one and not<br>
> only when fully implemented.<br>
> <br>
> Is this what we all agree on?<br>
> <br>
> Thanx,<br>
> Tomas<br>
> <br>
> ----- Original Message -----<br>
> > From: "Tomas Jelinek" <<a href="/compose?To=tjelinek@redhat.com">tjelinek@redhat.com</a>><br>
> > To: "Martin Betak" <<a href="/compose?To=mbetak@redhat.com">mbetak@redhat.com</a>><br>
> > Cc: movirt@ovirt.org, "Michal Skrivanek" <<a href="/compose?To=michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>>,<br>
> > bolya2003@bk.ru, "Yixin Zhang"<br>
> > <<a href="/compose?To=yixin_1992_cia@126.com">yixin_1992_cia@126.com</a>><br>
> > Sent: Tuesday, May 26, 2015 4:19:56 PM<br>
> > Subject: Re: [moVirt] when connection fails, user does not know the data<br>
> > are old<br>
> > <br>
> > <br>
> > <br>
> > ----- Original Message -----<br>
> > > From: "Martin Betak" <<a href="/compose?To=mbetak@redhat.com">mbetak@redhat.com</a>><br>
> > > To: "Michal Skrivanek" <<a href="/compose?To=michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>><br>
> > > Cc: "Tomas Jelinek" <<a href="/compose?To=tjelinek@redhat.com">tjelinek@redhat.com</a>>, bolya2003@bk.ru, "Yixin Zhang"<br>
> > > <<a href="/compose?To=yixin_1992_cia@126.com">yixin_1992_cia@126.com</a>>, <a href="/compose?To=movirt@ovirt.org">movirt@ovirt.org</a><br>
> > > Sent: Tuesday, May 26, 2015 2:35:22 PM<br>
> > > Subject: Re: [moVirt] when connection fails, user does not know the data<br>
> > > are old<br>
> > > <br>
> > > When I read the problem first that I thought was your last option. I<br>
> > > think<br>
> > > it's more then intuituve. Why don't you like it?<br>
> > <br>
> > just not sure how much space can we use on a small mobile display. But<br>
> > still<br>
> > the best thing I can imagine so far<br>
> > <br>
> > > It also could be combined with greying item if connection reports an<br>
> > > error<br>
> > > while updating entity.<br>
> > <br>
> > yes, combining it with the greying out all the items seems as a good option<br>
> > <br>
> > > <br>
> > > <br>
> > > <br>
> > > ----- Original Message -----<br>
> > > > From: "Michal Skrivanek" <<a href="/compose?To=michal.skrivanek@redhat.com">michal.skrivanek@redhat.com</a>><br>
> > > > To: "Tomas Jelinek" <<a href="/compose?To=tjelinek@redhat.com">tjelinek@redhat.com</a>><br>
> > > > Cc: "Martin Betak" <<a href="/compose?To=mbetak@redhat.com">mbetak@redhat.com</a>>, "Martin Beták"<br>
> > > > <<a href="/compose?To=matobet@gmail.com">matobet@gmail.com</a>>,<br>
> > > > bolya2003@bk.ru, "Yixin Zhang"<br>
> > > > <<a href="/compose?To=yixin_1992_cia@126.com">yixin_1992_cia@126.com</a>>, <a href="/compose?To=movirt@ovirt.org">movirt@ovirt.org</a><br>
> > > > Sent: Tuesday, May 26, 2015 11:06:46 AM<br>
> > > > Subject: Re: [moVirt] when connection fails, user does not know the<br>
> > > > data<br>
> > > > are old<br>
> > > > <br>
> > > > <br>
> > > > On May 26, 2015, at 11:04 , Tomas Jelinek <<a href="/compose?To=tjelinek@redhat.com">tjelinek@redhat.com</a>> wrote:<br>
> > > > <br>
> > > > > Hey All,<br>
> > > > > <br>
> > > > > we have an interesting bug report from Sandro [1] which says that<br>
> > > > > after<br>
> > > > > the<br>
> > > > > connection between engine and moVirt goes down, moVirt does not<br>
> > > > > notify<br>
> > > > > the<br>
> > > > > user about this and keeps showing the<br>
> > > > > old data in the UI as if nothing happened even they are weeks old.<br>
> > > > > This<br>
> > > > > is<br>
> > > > > obviously not correct but not exactly clear how should it behave. I<br>
> > > > > see<br>
> > > > > this options:<br>
> > > > > <br>
> > > > > - if the connection fails during the refresh, set all the statuses of<br>
> > > > > everything to "unknown"<br>
> > > > > (I would not do this since this would generate the notifications and<br>
> > > > > may<br>
> > > > > be temporal (e.g. phone in tunnel or something))<br>
> > > > > <br>
> > > > > - leave the data as they are and have some top bar or something<br>
> > > > > saying<br>
> > > > > how<br>
> > > > > old the data are. This would be updated at every poll<br>
> > > > > (Not sure, would occupy place and would make it hard for partial<br>
> > > > > updates.<br>
> > > > > And track this for each entity is costy)<br>
> > > > > <br>
> > > > > - leave the data as they are and if some server communication fails<br>
> > > > > add<br>
> > > > > a<br>
> > > > > top bar with a warning that the connection to server is lost and the<br>
> > > > > data<br>
> > > > > are old - maybe with some note when was the last successful<br>
> > > > > connection.<br>
> > > > > (this seems simple enough and my favorite but still not convinced I<br>
> > > > > like<br>
> > > > > it…)<br>
> > > > <br>
> > > > how about greying out the outdated data a little, after some period?<br>
> > > <br>
> > > This would require tracking of "last updated" timestamp for each tracked<br>
> > > entity<br>
> > > and as Tomas mentioned this would be somewhat costly (but maybe not<br>
> > > prohibitively).<br>
> > > <br>
> > > My suggestion would probably be a single global timestamp (last<br>
> > > successful<br>
> > > request)<br>
> > > and have this displayed *always* as a little non-obtrusive footer in each<br>
> > > activity.<br>
> > <br>
> > not sure how much non-obtrusive it will be if it will be there all the time<br>
> > changing after each action you do...<br>
> > <br>
> > > In case a request fails we can make it more prominent (bigger and with<br>
> > > cause<br>
> > > of last<br>
> > > error) so the user knows what is going on.<br>
> > <br>
> > I would show it only when there is an error and show the specific error<br>
> > only<br>
> > after the user clicks it.<br>
> > <br>
> > > <br>
> > > Having always readily available how old the data is will also serve as a<br>
> > > simple<br>
> > > check that the periodic refresh is working.<br>
> > <br>
> > yeah, but this is useful for development and not so much for the user I'd<br>
> > say.<br>
> > <br>
> > > > <br>
> > > > > <br>
> > > > > Any more ideas?<br>
> > > > > <br>
> > > > > Thanx,<br>
> > > > > Tomas<br>
> > > > > <br>
> > > > > <br>
> > > > > [1]: <a href="https://github.com/matobet/moVirt/issues/66" target="_blank">https://github.com/matobet/moVirt/issues/66</a><br>
> > > > > _______________________________________________<br>
> > > > > moVirt mailing list<br>
> > > > > <a href="/compose?To=moVirt@ovirt.org">moVirt@ovirt.org</a><br>
> > > > > <a href="http://lists.ovirt.org/mailman/listinfo/movirt" target="_blank">http://lists.ovirt.org/mailman/listinfo/movirt</a><br>
> > > > <br>
> > > > <br>
> > ><br>
> > _______________________________________________<br>
> > moVirt mailing list<br>
> > <a href="/compose?To=moVirt@ovirt.org">moVirt@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/movirt" target="_blank">http://lists.ovirt.org/mailman/listinfo/movirt</a><br>
> > <br>
> _______________________________________________<br>
> moVirt mailing list<br>
> <a href="/compose?To=moVirt@ovirt.org">moVirt@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/movirt" target="_blank">http://lists.ovirt.org/mailman/listinfo/movirt</a><br>
> <br>
_______________________________________________<br>
moVirt mailing list<br>
<a href="/compose?To=moVirt@ovirt.org">moVirt@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/movirt" target="_blank">http://lists.ovirt.org/mailman/listinfo/movirt</a></div></div></div></div></blockquote></BODY></HTML>