[BACK]Return to HTFTP.html CVS log [TXT] [DIR] Up to [Public] / libwww / Library / src
File:  [Public] / libwww / Library / src / HTFTP.html
Revision 2.24: download - view: text, annotated - select for diffs
Tue Jun 27 20:19:08 1995 UTC (28 years, 11 months ago) by frystyk
Branches: MAIN
CVS tags: v3/1pre2, NT, HEAD
no more cern stuff :-)

<HTML>
<HEAD>
<TITLE>FTP access module for libwww</TITLE>
<NEXTID N="z1">
</HEAD>
<BODY>

<H1>FTP access functions</H1>

<PRE>
/*
**	(c) COPYRIGHT MIT 1995.
**	Please first read the full copyright statement in the file COPYRIGH.
*/
</PRE>

This is the FTP load module that handles all communication with
FTP-servers. <P>

<B>Authors</B><P>

<UL>
<LI>Tim Berners-lee, timbl@w3.org
<LI>Denis DeLaRoca 310 825-4580, CSP1DWD@mvs.oac.ucla.edu
<LI>Lou Montulli, montulli@ukanaix.cc.ukans.edu
<LI>Foteos Macrides, macrides@sci.wfeb.edu
<LI>Henrik Frystyk, frystyk@w3.org
</UL>

This module is implemented by <A HREF="HTFTP.c">HTFTP.c</A>, and it is
a part of the <A
HREF="http://www.w3.org/hypertext/WWW/Library/User/Guide/Guide.html">
Library of Common Code</A>.

<PRE>
#ifndef HTFTP_H
#define HTFTP_H

#include "HTChunk.h"
#include "HTAccess.h"
</PRE>

<H2>Public Functions</H2>

Theese are the public functions...

<H3>Accessing FTP-Server</H3>

<PRE>
GLOBALREF HTProtocol HTFTP;
</PRE>

<H3>Enable/Disable Reuse of Control Connections on Client Side</H3>

The next two functions are for enabling and disabling reuse og control
connections on client side. Though, this is a temporary solution as the
library is going to be multi-threaded and then the control of open
connections changes. Reuse of control connections is mainly intended for use
when loading several files from the same server in the same directory, but
changing directory IS supported using FTP-commands CDUP and CWD.

<PRE>
extern void HTFTP_enable_session NOPARAMS;
extern BOOL HTFTP_disable_session NOPARAMS;
</PRE>

<H3>Various Functions to parse information</H3>

Theese functions are necessary in order to keep the internal data structures
hidden.

<PRE>
extern HTChunk *HTFTPWelcomeMsg PARAMS ((HTNetInfo *data));
extern BOOL HTFTUseList PARAMS ((HTNetInfo *data));
</PRE>

<H2>Flags for FTP connections</H2>

Those are the flags for configuring the FTP client.

<PRE>
extern BOOL HTFTPUserInfo;
extern long HTFTPTimeOut;
</PRE>

If HTFTPUserInfo = YES (as pr default) then the users login name and password
is reused when conneting to the same host. It is, however, overwritten by any
userid and passwd specified in the URL. This is only for the client side, as
server forks itself on any request. If this flag is not set, then anonymous
and username of the current proces is used. <P>

In addition, the following defines are available in the module: <P>

<DL>
<DT>LISTEN 
<DD>This defines makes it possible to use PORT and hence do an passive
open for the data connection. Though, if defined, this is only used AFTER
an active open has been tried using PASV.
<DT>REPEAT_PORT
<DD>If LISTEN is defined, then when we have found a passive port, then reuse
it for the next time, else we ask the system to get a new one.
<DT>POLL_PORTS
<DD>If the system doesn't support finding a new port, then let's try it
ourselves.
</DL>


<PRE>
#endif
</PRE>
end of HTFTP Module
</BODY>
</HTML>
Webmaster