On Thu, 2004-12-02 at 14:13 +1100, Peter Harvey wrote: > While the file broker idea sounds very nice, what of the more advanced > aspects of HTTP than just 'GET' requests? How will we handle cookies? Or > authentication? > > Unless the Epiphany project itself provides the backend downloader (via > embedded Mozilla code) I think we'll see problems in the implementation. > For that reason, maybe this project does belong in Epiphany (as the home > of Mozilla-in-Gnome). Thoughts? Beats me. Curl (http://curl.haxx.se/) can do GET and POST, cookies, and authentication. With enough fringe case testing, it might be possible to get a browser-independent backend working 100%. However, we'd need to have a knowledgeable programmer -- in both "real" HTTP and "the fucked up world we live in" HTTP. (Plus FTP, HTTPS, etc....) Maybe all the missing functionality could be integrated into GnomeVFS? It already has HTTP authentication, but not cookies I don't think (and judging by a TODO in http-method.c, it doesn't yet support redirection or persistent connections). I googled unsuccessfully for a GnomeVFS mission statement, so I don't know if all this functionality belongs. Would it be worth looking into? Is GnomeVFS supposed to be able to provide *all* the services Mozilla provides in terms of downloading? Some Bugzilla searching reveals: - http://bugzilla.gnome.org/show_bug.cgi?id=114632 - http://bugzilla.gnome.org/show_bug.cgi?id=61165 - http://bugzilla.gnome.org/show_bug.cgi?id=130336 Really, Epiphany isn't designed to be "Mozilla-in-GNOME". It's designed to be "Browser-in-GNOME" (emphasis on GNOME), and Mozilla is used because it's the only option. I think it'd be awesome for downloads to be independent of the browser -- as long as the integration is seamless, of course. -- Adam Hooper <adamh densi com>
Attachment:
signature.asc
Description: This is a digitally signed message part