Well, in theory - yes, in practice, it ain't so easy. The NodeInfoServlet resides on port 8890, that is the thing that draws the nice menu to the left, and can't really support controlling of the entire web-browser window, which is why we need FProxy.
Now, we could - say - set it up so that going to : http://localhost:8890/fproxy/CHK%40... Works like going to: http://localhost:8888/CHK%40... does now - however we would no-longer be able to take advantage of links to the server root (ie. hyperlinks which begin with "/"). That would be unfortunate. I guess we could also determine in real-time whether the URL looks like an FProxy link, or whether it looks like a NodeInfoServlet link. Ian. On Wed, Sep 04, 2002 at 11:27:22PM -0400, Dan Merillat wrote: > Ok, let it be said I love the new UI. However, since :8888 is just > redirecting > to :8890, can't we just merge the two interfaces? > > It screws up my setup of using squid to redirect freenet requests, but I > think I > can work around it. Perhaps. It's a pain to rewrite URLs on the fly, so I > may have > to maintain diffs to the source (UGH). -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ Personal Homepage http://locut.us/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020904/b16cb37d/attachment.pgp>
