[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: javascript and konqy?
From:       Alex Zepeda <garbanzo () hooked ! net>
Date:       1999-06-12 0:32:09
[Download RAW message or body]

On Fri, 11 Jun 1999, Matt Koss wrote:

> That's needed, of course.
> I have only put some options quickly into KProtocolManager for ftp and http
> proxy.

Right, and this is why I think a more abstracted interface would be a good
thing.

> BTW, will anybody take a look into ftp-proxy slave ?
> Some code is there in kioslave/ftp, but I am really not an expert on this.

This is not the feeling that I get.  From the fetch man page:

     The FTP proxy client passes the remote username, host and port as the FTP
     session's username, in the form ``remoteuser@remotehost[@port]''. The
     HTTP proxy client simply passes the originally-requested URI to the re-
     mote server in an HTTP ``GET'' request.

I general HTTP proxies can be used to proxy nearly any TCP protocol, and
fetch will use the HTTP proxy for ftp too if it's set (which irks me to no
end).

> In KDE 1.1, ftp-proxy protocol is a subclass of http protocol.
> I don't think that we could use a same approach now, or could we ?

Actually yes it probably could, but it might involve extending KURL to
support "options".  Sure one could tack on ?foo=bar&baz=foo *but* this
doesn't work with the HTTP protocol, as it already parses those.

A better idea would be to perhaps try and use http as a source protocol..

- alex

I thought felt your touch
In my car, on my clutch
But I guess it's just someone who felt a lot like I remember you.
  - Translator

[prev in list] [next in list] [prev in thread] [next in thread]