On Wednesday 17 June 2009 13:27:10 sashee wrote: > Hello everybody! > > This is time for my first status report, because mid-term evals are > approaching. > > Some introduction, what I'm doing exactly. My project is to introduce > web pushing to the web interface. That actually means, that the data > displayed are refreshed automatically, without the need to refresh the > whole page. It is accomplished with ajax requests and javascript at > the client side, and some toadlets at the serverside. Toad had a > concern about the number of opened connections, so a connection > sharing mechanism is also a requirement. This connection sharing > ensures that only 1 permanent connection is used per browser, no > matter how many tabs are open. Another requirement is that the web > interface must be usable when javascript is disabled(but pushing wont > work that way) > > About my current status:I've created the basic infrastructure both > server and client side, so pushing works and connection sharing also.
Great! You have tested this? > Currently only the progress bar on the progress page is pushed, but it > nicely visualize the feature. The client side is written in java, and > transformed to javascript with the help of the GWT compiler. Very nice. > > How to check the current status: > Pull and checkout to the web-pushing branch, then build the project. > Please don't distclean, because it will delete the generated > javascript, and you won't be able to generate it yourself atm. Then > start Freenet, and open a browser with it. You have to enable > javascript both on your browser and on Freenet. Now you should browse > Freenet, and see the progress bar is updating, and when the loading is > ready, you get the page you just fetched. I've put some tester > elements at the status page, they are increased by 1 every second. > They help to see bugs, as they use pushing heavily. > > I've tested it at Firefox both windows and linux, and IE7. They worked > well, although testing on other systems would be helpful. Chrome compatibility is important. The current progress bar javascript doesn't work on Chrome, we have to detect AppleWebKit (also used for Safari, default browser on OS/X) and fall back to a refresh at the moment. Chrome is important because it is the only currently shipping browser to have an incognito mode; hence, on Windows, if Chrome is installed, we use it. Hopefully GWT solves the compatibility issues the hand-crafted code has, but we need to verify this. > > Please don't use pushing, just for testing and reviewing. It has some > major bug that needs to be addressed. But feedback is always > appreciated. > > What's next? > As I've 3 weeks before mid term eval, I'll fix the known bugs and > optimize some processes, and it also needs be documented and > commented. The pushing can also be used for the images' loading, but > I'll write a separate email about that. That would be very helpful yes, probably more important than the original project of making the various status pages dynamically update. Apologies for not reviewing/testing your code so far, have been busy with the release. I'm not here from the 20th to the 27th so I will try to review all recent changes, especially for my SoC students, and test the code where possible. > > 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/20090617/e4b557c3/attachment.pgp>
