tis 2014-01-21 klockan 14:37 -0700 skrev Alex Rousskov:
[FWIW, the term FTP Gateway was suggested by Henrik during initial RFC
review. Henrik thought that using HTTP semantics internally means we are
a gateway. I changed the project name in order to avoid having an
argument. Technically, it is
On 01/20/2014 08:45 PM, Alex Rousskov wrote:
Hello,
FTP gateway[1] code[2] work well, and we are polishing it for the
official submission. The biggest change we need to make is to rearrange
where the new code lives in Squid src directory. In this email, I am
proposing how to structure
mån 2014-01-20 klockan 11:45 -0700 skrev Alex Rousskov:
FTP gateway[1] code[2] work well, and we are polishing it for the
official submission. The biggest change we need to make is to rearrange
where the new code lives in Squid src directory.
For the record I have no opinion on either of
[ A specific revised proposal is at the end of this email, after the
discussion. ]
On 01/20/2014 03:30 PM, Amos Jeffries wrote:
On 2014-01-21 07:45, Alex Rousskov wrote:
I propose the following arrangement for the official submission:
src/out/FtpServer.* # code shared by old and new FTP
On 2014-01-22 10:37, Alex Rousskov wrote:
[ A specific revised proposal is at the end of this email, after the
discussion. ]
On 01/20/2014 03:30 PM, Amos Jeffries wrote:
On 2014-01-21 07:45, Alex Rousskov wrote:
I propose the following arrangement for the official submission:
On 01/21/2014 03:54 PM, Amos Jeffries wrote:
[ On a side note shall we make a proper effort to fix that confusion by
deprecating our use of the terms and call bits client or server by
functionality? it would be as easy to describe these area-based parts as
client-facing or server-facing areas
On 2014-01-21 07:45, Alex Rousskov wrote:
Hello,
FTP gateway[1] code[2] work well, and we are polishing it for the
official submission. The biggest change we need to make is to rearrange
where the new code lives in Squid src directory. In this email, I am
proposing how to structure that new
