Oskar Sandberg <oskar at freenetproject.org> wrote: > On Tue, Jun 26, 2001 at 06:03:10PM +0100, Theodore Hong wrote: > > no, I mean feedback during requests, e.g. some kind of timer counting down > > and getting bumped up when QueryRestarted's come back. Maybe somehow > > seeing whether the node is just waiting for a reply to come back or whether > > it hit some bug and crashed. > > I think this is extremely important. Nothing is less userfriendly then a > long unexplained wait. The proxy should keep people informed at what is > going on, especially if you get a QueryRestarted. > > If you set Content-type: text/html browsers will start displaying before > the page has finished loading, so you can just do the counter as a > series of characters slowly written to the message body, then at the end > you put a link to a page with the actual data.
That is, in fact, the way I wrote it in the first place. =) Except I made it dump the log to the output (hence the HtmlLogger class). It causes trouble with inline images though. What I'm envisioning now is a single separate popup window for the entire browsing session (perhaps Javascript'ed in gateway.html) which requests a special URL from fproxy. The browser gets back a text/html document which never ends, it just keeps feeding back status data for the requests you are doing in the other windows. theo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 174 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010628/efd52a00/attachment.pgp>
