Hello folks I've been busy with my final thesis as you've probably noticed and couldn't make progress to fix and stabilize the web-pushing functionality. The #1 problem with it is that it has became a maintenance nightmare to keep the branch up-to-date. Every few change makes conflicts and after some time it takes nearly hours to fix all of them, and it is really error-prone. After a few weeks, I've started to fix bugs, just to found out I can't even connect to other peers, saying they are too new. It makes development very hard, and full of non-related tasks.
One of the cornerstone of the development was that all functionality must work as of now when javascript is disabled, so this whole web-pushing is an optional feature. Imo the course to take is to test throughly that it works fully with web-pushing disabled and merge it back to the master and the development can resume on that branch without the burden of constantly keeping it up-to-date with the ever-increasing difference from the master. Users may not notice anything, and when it is finally ready, it can be enabled with a single commit to everybody. About it's current status: - I'm pretty sure that the client side code is stable, both event receiving and processing, and connection sharing-vise. - The server side has some bugs that causes stallings and exceptions, and they are hard to discover and fix. Most of the remaining work is to fix them. - There are some architectural flaws that may cause events to be lost, although they are not hard to fix. The XHTML support is still broke, and most likely will be in the future, as folks at GWT thinks it is low priority ( http://code.google.com/p/google-web-toolkit/issues/detail?id=710 ). As the XHTML standard is considered low-priority at W3C in favor to HTML5, I think treating XHTML as HTML(as of now) won't break sites, and GWT is happy too. Thoughts welcome sashee On Sat, Nov 21, 2009 at 11:23 PM, Matthew Toseland <[email protected]> wrote: > On Saturday 21 November 2009 18:03:59 Evan Daniel wrote: >> On Sat, Nov 21, 2009 at 12:39 PM, Matthew Toseland >> <[email protected]> wrote: >> > There are a number of reasons why the web-pushing branch should be merged >> > before 0.8 if at all possible: >> > - pupok is working on a mockup of a GWT-based UI redesign for fproxy. >> > - It enables us to use the new minimalist theme and/or to use activelinks >> > in any new UI. >> > - It solves some big browser connection limit related problems with image >> > loading. >> > - It solves the current loading-a-page javascript not working with Chrome. >> > - It solves some minor problems with the current javascript code >> > (sometimes the last refresh fails) >> > - It allows this-page-is-updated notifications. >> > >> > Thoughts? >> >> Have the XHTML issues been resolved? > > No. >> >> Has progress been made on packaging GWT so that distros can build >> Freenet cleanly? > > No. We don't have packages at the moment, except the gentoo one. The level of > benefit from the gentoo package is not high enough to justify not using GWT, > even if using GWT would prevent us having a gentoo package, which it > shouldn't. On other systems, we will, intentionally, not have an official > package in the official repo for a long time. > > _______________________________________________ > Devl mailing list > [email protected] > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > _______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
