I agree, yet I think we'd need more info on how to proceed regarding this one.
>From my testing, here is what I see: when disconnecting for a small period of time, like less than 30 seconds, connection resumes successfully for me, otherwise connection is lost and xfreerdp closes. There is some confusion around the reconnection token, which is a new feature. I'm not sure how exactly we should detect that connection has been lost, and how fast we should detect it. Should we have a thread watching the connection status and reconnecting if the connection is lost? What happens if the connection was not lost, but the server intentionally disconnected the user? What about server redirection, where multiple connections are done in sequence? What constitutes being fully connected, such that if we lose that connected state we should normally attempt to reconnect? This feature is more complex than I originally thought, which is probably why it hasn't been completed yet. Help is welcome, of course. I think we could likely have it for 1.0.1 and make it a priority. On Sun, Jan 15, 2012 at 2:49 PM, Anna Martynova <terrible.br...@gmail.com>wrote: > I'm absolutely agree with Gotsi Boon! > I know people who prefer Freerdp to Rdesktop mainly because of this — > Freerdp didn't freeze in case of network faults. > I think it's very important in everyday usage. > > 2012/1/14 Gotsi Boon <gotsi.b...@gmail.com>: > > Hi Marc-Andre, > > > > if I take a look at the list the blocker #189 "X11 client freezes > > indefinitely if connection is lost" sounds like a severe issue for > > productivity usage. > > > > Best regards, > > gotsiboon. > > > > > > On Sat, Jan 14, 2012 at 6:08 AM, Marc-André Moreau > > <marcandre.mor...@gmail.com> wrote: > >> > >> Hello FreeRDP community, > >> > >> We've been working hard lately to stabilize FreeRDP in preparation for > the > >> 1.0 stable release. We're currently in beta5, but I do not think we can > >> release betas forever like this. Important regressions were left to be > >> fixed until today, but now I feel that we have something good enough to > be > >> released. The last two major issues which I really wanted to have fixed > >> were the sporadic bitmap cache faults and the VRDP connectivity issue, > both > >> of which were fixed this week. > >> > >> I know that there are still some bugs with red labels on the bug > tracker, > >> but I think we now have something good enough for most people. If there > is > >> something that I've learned spending months bug fixing stuff is that > >> stability really is something valuable :) For this reason I would like > to > >> propose the following branching strategy, quite similar to the > >> "maintenance" branch which we once had: > >> > >> For each stable release, we should create a new branch. This means that > >> when releasing 1.0 stable, we would create a "1.0" branch. The current > >> master will then become the future "1.1" branch, and will get all the > new > >> features and bug fixes. The 1.0 branch would not get the new features, > but > >> only bug fixes, such that can keep it stable and make maintenance > releases, > >> such as "1.0.1". > >> > >> When it will be time to make the 1.1 stable release, we will create a > "1.1" > >> branch as well, and master will become the future "1.2" branch. At this > >> point we would maintain the 1.1 branch for maintenance releases but stop > >> maintaining the previous stable release (unless we want to start doing > >> maintenance releases for multiple past stable releases, which is a lot > of > >> work). > >> > >> I think the maintenance releases will lead to rock solid versions of > >> FreeRDP which should satisfy a lot of people looking for > production-ready > >> code. The development releases will keep satisfying those of us looking > for > >> the latest and coolest features :) > >> > >> Would anybody have strong objections to a 1.0 stable release at the > >> beginning of this week? If there are still some bugs which prevent you > from > >> using the soon-to-be 1.0 stable release, they should be addressed in the > >> 1.0.1 maintenance release. We won't suddenly stop fixing bugs just > because > >> we have a stable release if this is your concern. > >> > >> Comments are welcome, > >> > >> Best regards, > >> - Marc-Andre > >> > >> P.S.: I desperately need help with Remmina development, if you'd like to > >> help me out then contact me, thanks! The deadline for inclusion in > Ubuntu > >> 12.04 is getting closer and I'd need to get Remmina updated for 1.0, but > >> I'm truly overworked. > >> > ------------------------------------------------------------------------------ > >> RSA(R) Conference 2012 > >> Mar 27 - Feb 2 > >> Save $400 by Jan. 27 > >> Register now! > >> http://p.sf.net/sfu/rsa-sfdev2dev2 > >> _______________________________________________ > >> Freerdp-devel mailing list > >> Freerdp-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > > > > > > > > -- > > > > No §112! > > > > > ------------------------------------------------------------------------------ > > RSA(R) Conference 2012 > > Mar 27 - Feb 2 > > Save $400 by Jan. 27 > > Register now! > > http://p.sf.net/sfu/rsa-sfdev2dev2 > > _______________________________________________ > > Freerdp-devel mailing list > > Freerdp-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > _______________________________________________ > Freerdp-devel mailing list > Freerdp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
