On Wednesday 24 June 2009 13:08:02 sashee wrote: > Hello all! > > I'm going to have a holiday lasts from tomorrow, till 30 jun, so I'll > be unavailable that time. But because the mid term evals are coming, I > write a second status report before leaving. So here is a summary what > I've been working on the last week:
Welcome back. :) > > I've investigated the onUnload events and seems to be working nicely, > and GWT supports it as well. It would became the primary way of > detecting tab closes and the periodic keepalives will be a > supplementary method which detect crashes. It will come at handy with > the image loading, so the fetches will be interrupted when the user > closes the tab. Yes, this is good. > > Autotests: In most of my time, I've written an auto-test suite for > pushing. It requires fproxy to be running. I have written a tester > toadlet, that has some pushed data that changes, and also some tests > that tries some functionality. The problem is, that they needs > additional libraries, and it shouldn't be part of the standard build > process, because it lasts very long(atm ~1.5 minutes, but it is just 4 > tests!). On the other hand, it will help stabilizing the API and make > sure no previous functionality broke when new added. What additional libraries? More GWT stuff? > > I've rewritten the scheduler to use the Ticker instead of Timer. It is > now working, but I found a bug that needs fixing in some way. Please > see commit 84396b8b0f539ee4351c521641b5f482e1961847 , I've written a > short description about it. It should be fixed either by deleting the > functionality(it's not working, so it won't be missing), or fix it, > but that will consume some resources. Will look into this. > > I've rethought thread synchronization at the pushing, and now just > synced all methods. It is much easier and bug-proof and won't degrade > performance as all methods return quickly. > > As I'm making more and more toadlets and other files, I'm feeling the > need to put all of them to a different package(ajaxpush), but I've > already created them. Is there a way in git to move files preserving > history? I think you have done this ... > > > What will come int the next month: > First thing first, currently only the progress bar is updated. I'll > make that other fields on that page will be too(the timer, and the > file size as it become known). That is working, tested, very impressive (modulo bugs). If you do get this to a reasonably stable point where it could be merged, it might be worth considering ... > Next, the image loading, that fetches all images concurrently when the > page is loaded, then updates all status, and when leaving the page, > cancels. Yep, this is very important. > The downloads page and the connections page should also be pushed, as > they are changing frequently. These are in fact four pages. > The message handling should have some improvements, like get messages > when browsing freenet, and they should be pushed. There are other areas that could be improved (e.g. push on the messages page / homepage), but the above is plenty. The architecture might be a bit different for messages, whether they are pop-up-like/hover-over, or whether they are being added on the messages page or the home page, since we'd be adding whole new elements?? > > As always, feedback are welcome, but I most likely won't be able to > check my mails in the following days. > > sashee -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090703/072ef30d/attachment.pgp>
