# 
# Viador FTP Server
# Readme.txt
# Code Drop #41 
# Date: Friday, September 26th, 2008
#

Changes from Previous Drop
-------------------------------
    > IPV6: Support to the IPV6 environment and switch the mode between running as the regular ftp server with support for cmd ftpclient and the encrypted ftp server

    Files Affected:
	viador\atlas\ftpclient\FtpClient.java
	viador\atlas\server\Server.java
	viador\atlas\server\Listener.java
	viador\atlas\servlets\UploadServlet.java
	viador\atlas\session\Session.java
	viador\atlas\session\FTPCommand.java
	viador\atlas\session\StateManager.java
	viador\atlas\session\DataTransferProcess.java
	viador\atlas\test\FtpThread.java
	viador\atlas\util\MessageHandler.java
	viador\atlas\util\MessageCode.java
	viador\api\User.java
	infospc\SessionMgr\ISSession.java


------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #41 
# Date: Friday, September 11th, 2008
#

Changes from Previous Drop
-------------------------------
    > FIPS1402: Add ecrypted messages and Sequence Number between the FTP Client and the FTP Server.
		The format of the messages is " Sequence Number+CMD+Data",for example,1589687320 USER administrator, before ecrypted by AES.

      Files Affected:
      viador\atlas\ftpclient\FtpClient.java
      viador\atlas\server\Server.java
      viador\atlas\server\Listener.java
      viador\atlas\servlets\UploadServlet.java
      viador\atlas\session\Session.java
      viador\atlas\test\FtpThread.java
      viador\atlas\util\MessageHandler.java
------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #40 C
# Date: Wednesday, December 20th, 2000
#

Changes from Previous Drop
-------------------------------
    >  The JDK 1.3 problem with the BufferedReader has been fixed. The user has to specify the system property with the
       -D option. If the version is JDK 1.3 then the user has to set the property 
       'Reader.class = viador.atlas.io.BufferedReader' as shown

        java -ms64m -mx128m -DReader.class=viador.atlas.io.BufferedReader viador.atlas.server.FTPServer start 9000 localhost 6889 d:\inetpub\wwwroot\infospc\
	
	In other cases, if the property is not set, then the default java.io.BufferedReader is used.	

    >  Some clean up has been done in the code to close the streams properly.
    >  Problem in ASCII download has been fixed. The ASCII download was done by reading a line at a time, this has been modified to read in junks of 4K to improve the performance of ascii download.

        Files Affected:
	viador\atlas\io\BufferedReader.java
	viador\atlas\io\AZBufferedReader.java
	viador\atlas\io\makefile
	viador\atlas\server\Console.java
	viador\atlas\server\CloseServer.java
	viador\atlas\server\Listener.java
	viador\atlas\servlets\UploadServlet.java
	viador\atlas\session\DataTransferProcess.java
	viador\atlas\session\Session.java
	viador\atlas\session\Upload.java
	viador\atlas\util\ftputil.java
	viador\atlas\util\TemplateHandler.java

------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #40 B
# Date: Friday, December 7th, 2000
#

This drop contains the changes done on drop #40A sent by viador on 11/23/00.


Changes from Previous Drop
-------------------------------
    >  When a user is killed abnormally using Ctrl-C, the dtp connection was not being closed during an upload or a download.
    >  Problem in ASCII upload has been fixed. The ASCII upload was done by reading a line at a time, this has been modified               to read in junks of 4K to improve the performance of ascii upload

        Files Affected:
	viador\atlas\session\Session.java
	viador\atlas\session\DataTransferProcess.java
	viador\atlas\session\Upload.java
	viador\atlas\servlets\UploadServlet.java

Note:
------
   The UploadServlet.java and makefile is of the code drop # 38. If this is used the other files
   (FtpClient , FtpConnectionException, FtpProtocolException) should be removed. Otherwise the 
   UploadServlet.java of the code drop #40 should be used.

------------------------------------------------------------------------------------------------------------------------
# 
# Viador FTP Server
# Readme.txt
# Code Drop #40 A
# Date: Friday, December 7th, 2000
#

We are identifying the source sent by Viador on 11/23/00 as drop #40A as this is not same as 
drop #40 sent by Aztec to Viador on 06/30/00.


(10) Changes from Previous Drop
-------------------------------
   > These changes have been made by viador

        Files Affected:
	viador\atlas\portal\Portal.java
	viador\atlas\servlets\UploadServlet.java
	viador\atlas\servlets\makefile
	viador\atlas\session\DataTransferProcess.java
	viador\atlas\session\Session.java
	viador\atlas\threadpool\ThreadPoolManager.java
	viador\atlas\util\MessageCode.java
	viador\atlas\util\MessageHandler.java


------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #40
# Date: Friday, June 30th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #40" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    >  The problem of the Threadpool has been fixed.

------------------------------------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #39
# Date: Thursday, May 31st, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #39" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    >  A Custom FTP Client has been integrated into the Upload Servlet to enable proper closing of FTP Connection

------------------------------------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #38
# Date: Thursday, May 26th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #38" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > The user limit can be configures in the FTP Server by setting the "maxConn" value in Universal.conf. If this value is
        not set, the default is 50.
        When this limit is reached, the user is given a message that the server is busy and to try again later.
         A similar error will be displayed in Sage Upload.
------------------------------------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #37
# Date: Thursday, May 23rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #37" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bugs Fixed: 
	13181 : In Sage Explorer Upload, the overwrite flag wont work even if there is any space 
	in the file name. The cause of the problem is the current UploadServlet file has assumed 
	the file name does not contain any space.
	
	13055 : We should not let user to rename special folders. i.e. if folder.isSpecialFolder( ) returns true,
	 ftpserver should deny the rename request.

	12842 : please only make sure CuteFTP is working fine

	The above bugs have been fixed.

------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #36
# Date: Thursday, May 11th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #36" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bug Fixed: 
          	While uploading files one at a time in Sage Explorer I have 
 	experienced the following limitation: Exactly 10 files can be 
 	uploaded during a single session. The upload utility hangs in 
 	the 11th file upload. Restarting the VIC does not solve the 
	problem. Restarting the VIC and Tomcat does solve the problem - 
	for another 10 file uploads.

	Changes have been made to the FTP code to fix this problem.

------------------------------------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #35
# Date: Thursday, April 15th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #35" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bug Fixed: 
          FTP was not support filename with space in it. For e.g., command put "Test2 .log" was failing.
          Related problem found and fixed are
            LIST or NLIST was not displaying filename with space trimmed.
            DEL/REN command was not deleting filename with space
            MPUT/MGET were not handling filename with space in it.
          	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #34
# Date: Thursday, April 11th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #34" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bug Fixed: 
	When there are multiple users with the same "user name" logged in, a 'kill user' command on the console
	does not kill all the users.
           	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #33
# Date: Thursday, April 06th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #33" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.

  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\startftpserver.bat  - Batch file for running the server.
  > viador\stopftpserver.bat  - Batch file for stopping the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> startftpserver

(6) Stopping the Server
-----------------------
  > The Server can be stopped by running the batch file 'stopftpserver'.
      for e.g., c:\viador> stopftpserver

(7) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(8) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(9) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(10) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())
  
  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Changes have been made to check for Channel creator before creating a new channel
           	
--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #32
# Date: Friday, March 24rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Changes have been made to call finalize of the util class to destroy the util object
      after the session ends
    > Changes have been made for authentication using LDAP. 
       	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #31
# Date: Thursday, March 23rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd31.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Changes have been made to upload a file without extension. 
       	
--------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #30
# Date: Tuesday, March 21th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Changes have been made to incorporate "My Channels"  and "My Folders". 
       	
--------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #29
# Date: Monday, March 20th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Changes have been made to incorporate "My Channels" .
    > The listening port of Ftp Server is configurable 	
    >  Uploading a file through Upload Servlet takes care of a unique file name for each user 
      	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #28
# Date: Wednesday, March 15th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Outsdtanding bugs have been fixed.
      	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #27
# Date: Tuesday, March 14th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bug No 10634 has been fixed
    > Bug No 10923 has been fixed.
      	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #26
# Date: Monday, March 13th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #26" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > Bug No 10375 has been fixed
    > Bug No 10923 has been fixed.
    >Bug No 10582 has been fixed.
  	
--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #25
# Date: Friday, March 11th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #24" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd25.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
    > BugNo 10808 has been fixed as the FileIfc.getPath() .    
  	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #24
# Date: Friday, March 10th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #23" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd24.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > the infoshutdown.bat has been changed to shutdown the Ftp server. 
  > The FTPServer listens on a port (which by default is 9000 on the localhost). 
    If the port number has been changed , the  stopftpserver.bat(and infoshutdown.bat) file has to be
    changed to provide the correct port number 
  > Bug No 10634 has fixed.    
  	
--------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #23
# Date: Friday, March 03rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #23" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd23.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > startftpserver.bat and stopftpserver.bat scripts have been provided. 
  > The FTPServer listens on a port (which by default is 9000 on the localhost). 
    If the port number has been changed , the  shopftpserver.bat file has to be changed
    to provide the correct port number 
      
  	
--------------------------------------------------------------------------------------------



# 
# Viador FTP Server
# Readme.txt
# Code Drop #22
# Date: Tuesday, February 29th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #22" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd22.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	
   
(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > Bug Fixes for
     1. Uploading a file based on the role of the user.
     2. Not permiting to delete a special directory.
     3. Changes with respect to default directories during upload using mput*.*    
	
--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #21
# Date: Monday, February 28rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #21" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd21.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.
   The Server (like all FTPServers) does not facilitate Appending to a binary file. 	

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > Bug Fixes for checking the role of the user.
	
--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #20
# Date: Thursday, February 24rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #20" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd20.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > Bug Fixes.
	
--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #18
# Date: Tuesday, February 15rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #18" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd17.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > The problems have been fixed , but not tested due to the unavailability of a    
    proper ePortal. See Bug Status report for details.

--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #17
# Date: Monday, February 7rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #17" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd17.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > Added additional functionality for WildCard Support.
    Capabilities:
      1> * .*
      2> * . a
      3> a . *
      4> *
      5>  a* . *
      6>  *a .*
      7>  * . a*
      8>  * . *a
      9>  a*
     10>  *a
   

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #16
# Date: Friday, February 4rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #16" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd16.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach more than
    10,the Util.init() method, hangs. This problem does not let further
     users to get authenticated. This persists until the Server is 
    restarted.( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. A message 'FINALIZING!' is seen in the console.


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
   

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #15
# Date: Thursday, February 3rd, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #12" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd15.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 and 9514
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
   

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #14
# Date: Tuesday, February 1st, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #12" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
   

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #13
# Date: Monday, January 31st, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #12" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
   

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #12
# Date: Wednesday, January 19th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #12" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
  > Performance analysis has been done extensively.
   

--------------------------------------------------------------------------------------------


# 
# Viador FTP Server
# Readme.txt
# Code Drop #11
# Date: Monday, January 17th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #11" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
    

--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #10
# Date: Friday, January 14th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #10" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Bugs have been fixed. (See Bug Report for details).
 
  

--------------------------------------------------------------------------------------------
# 
# Viador FTP Server
# Readme.txt
# Code Drop #9
# Date: Tuesday, January 11th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #9" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > Files can be uploaded to the root directory.

--------------------------------------------------------------------------------------------
# 
# Viador FTP Server
# Readme.txt
# Code Drop #8
# Date: Friday, January 7th, 2000
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #8" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\servlets
	    - Contains the Upload Servlet and its components


  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	    - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
	    - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
	    - Contains the Test Plan and Bug Status for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver.bat  - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  (see BugStatus in doc directory for details)
  > Only minimal support for Wild Cards is provided (ie only for directory llisting to                 facilitate mget/mdel *.xxx,xxx.*,*.* and * from MS-DOS FTP Client)

  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > SMR : 8926 
    There is no synchronization between FTP session and Portal Session. 

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 


(10) Changes from Previous Drop
-------------------------------
  > The command line parameters viador host name, port number and infospc root can be                     configured in the Universal.conf file.
  > REST (Restart command has been implemented.
  > Password authentication has been implemented.
  > Bug Fixes (see BugStatus for more information).

--------------------------------------------------------------------------------------------
# 
# Viador FTP Server
# Readme.txt
# Code Drop #7
# Date: Wednesday, December 29th, 1999
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs
  (10) Changes from Previous Drop	

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #7" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	          - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
		  - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
		  - Contains the Test Plan for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver      - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 
    > After uploading a file the return message contains the disk ID of the file.

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique) 
     7. From DOS FTP client , mget,mput,mdel commands can be used with 
        minimal support for wild cards. 	
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  > Only minimal support for Wild Cards is provided (ie only for NLST command to facilitate 
    mget/mdel *.xxx,xxx.*,*.* and * from MS-DOS FTP Client)

  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > When two concurrent users are in the same directory, if one uploads a file to the         server, the file does not appear in the file listing of the other user.
    A similar problem is faced during deletion of a file.

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 

  > The scalability of the server is lower than the previous build.

(10) Changes from Previous Drop
-------------------------------
  > File ID is included in the return message from the server, after a file has been     uploaded.
  > The command line parameters viador host name, port number and infospc root can also be         configured in the Universal.conf file.


--------------------------------------------------------------------------------------------

# 
# Viador FTP Server
# Readme.txt
# Code Drop #6
# Date: Thursday, December 24th, 1999
#

Contents
========
  (1) Introduction
  (2) Files and Folders
  (3) Makefiles
  (4) Building the Source Files
  (5) Running the Server
  (6) Server Capabilities
  (7) Testing the Server
  (8) Limitations
  (9) Outstanding Bugs

(1) Introduction
----------------
Viador FTP Server is a stand-alone FTP Server, which will be based on the
'RFC0959 - File Transfer Protocol' standard.  The Viador FTP Server uses 
the Viador User Manager API to verify security privileges and implement
folder/channel/file mappings based upon metadata stored in the Viador
repository.(Please refer the design document for more information on the
Viador FTP Server).

This document is the readme.txt for the "code drop #6" of the server, which
explains the limitations and outstanding bugs in this release.

(2) Files and Folders
---------------------
The code name for the FTP Server is 'atlas'. All the files are implemented
as a part of 'viador' package. The details of all the files in the package 
and the directory structure is as follows - 

Package: 
  > viador.atlas

Folders:
  > viador       
            - The root directory for the complete package.

  > viador\atlas
            - The root directory of the ftp server.

  > viador\atlas\server 
            - The folder contains the server and it's associated component
	            implementation.
  
  > viador\atlas\session
            - Contains the session, UserPI, UserDTP and State Manager 
              implementation.

  > viador\atlas\portal
            - Contains the implementation class for portal integration.

  > viador\atlas\threadpool
            - Contains the ThreadPoolManager and it's associated implementation.

  > viador\atlas\util
	          - Contains various utility implementations, like logmanager, 
              message handler.
  > viador\atlas\test
		  - Contains test suites to test various functionalities and the
	      scalability of the server.
  > viador\atlas\docs
		  - Contains the Test Plan for the FTP Server.

Files:
  > viador\ftpserver.mak  - Makefile for building the source files.
  > viador\ftpserver      - Batch file for running the server.

(3) Makefiles
-------------
    The server contains one root makfile, for building the complete Server, and
    one makefile in each sub-directory for building individual source files.
    The root makefile contains the following targets - 
    -- all          : Builds the server and upload files by invoking the 
                      individual makefile file.
    -- server       : Builds only the server.
    -- test	    : Builds only the test suites.
    -- clean        : Removes all the class files generated for server and test.
    -- serverclean  : Removes only the server class files.
    -- rebuild      : Removes all the class files and rebuilds the source files.
    

(4) Building the Source files
-----------------------------
  (A) Unzip the files into a folder using applications like unzip or winzip.
        for e.g., c:\viador> unzip ftpserver_cd6.zip
  (B) For building all the files (server and test), type the following command
        c:\viador> nmake /f ftpserver.mak
      For building only the server, type the following command
        c:\viador> nmake /f ftpserver.mak server
      
(5) Running the Server
-----------------------
  > The Server can be started by running the batch file 'ftpserver'.
      for e.g., c:\viador> ftpserver

(6) Server Capabilities
-----------------------
  This pre-release ftp server, is a multi-threaded model, where multiple users 
  can connect to the system at any given instance.
  The list of capabilities are as follows - 
 
  Server Capabilities
  -------------------
    > The Server is intergrated with the Portal.
    > User is authenticated using the Viador Information Server.
    > User can browse, create, delete and rename channel(s)/folder(s).
    > User can list, delete, upload, download and rename files.
    > User can save/open Office documents directly into the Viador's
      folder/channel.	
    > User can abort a file transfer using ABOR 
    > User can reinitialize to the initial status.
	Usage : quote REIN
    > Temp mode is implemented
	Usage: quote mode temp 

  Server Administration
  ---------------------
    -- The Administrator can view the status and details of all users( or of a particular 
	user) connected to the server
	Usage:
	>show <all | username>

    -- The Administrator can terminate all users (or a particular user) after an optional 
	waiting time(in milli seconds).
	Usage:
	>kill [wait_time] <all | username>

    -- The Server can be shutdown from the console.
       > Quit
       
  Directory Navigational Commands:
  --------------------------------
    Basic directory navigational commands are supported right now, from
    which the user can browse the directories, create a directory, etc.
    The list of commands supported are as follows:
       > MKD          - Create a directory.
       > RMD          - Remove a directory.
       > PWD          - Print working directory.
       > CDUP         - Cd to the home directory.
       > CWD <dir>    - Cd to directory specified in 'dir' variable.
       > PORT         - Specify the port in which the client will listen for
                        data transfer.
       > LIST         - List the contents of directory.
       > NLST         - List the contents of the directory, along with the
                        filesize.
       
   File Transfer Commands:
   -----------------------
     1. Files can be uploaded and downloaded to and from the server.
     2. Transfer Type can be ASCII or binary
     3. Transfer mode is Stream
     4. File structure can be transfered
     5. An existing file in the server can be appended. (APPE command)
     6. Files can be uploaded using unique names (see TF_StoreUnique)
    
   Miscellaneous Commands:
   -----------------------
     1. HELP                    - Provides a list of all the commands
     2. HELP [command] 		- Provides help on the command
     3. STAT [file/directory]   - Provides the status of the server/file/directory
     4. SITE			- Provides a list of special commands supported by this 
				  server (commands that are not present in the RFC 959)
     5. SYST			- Gives the operating system in which the server is running
     
(7) Testing the Server
----------------------
    MS - DOS FTP Client:
    --------------------
    The FTP Server can be tested with MS-DOS ftp client.
    
    MS-OFFICE:
    ---------- 
    The Server has been exhaustively tested with MSOffice, and no major bugs have been 
    found.
    
    Servlet-Upload:
    ---------------
    The Server works well with the servlet upload.

    Test Programs:
    --------------
    Test scripts are available in the viador.atlas.test package. Details about the tests are
    provided in the viador\docs\ftpsrv_testplan_1_1.doc

    Note: Please set the classpath in batch file appropriately before running
    the batch files.

(8) Limitations
---------------
   The Server has not been tested in UNIX platform.

(9) Outstanding bugs
--------------------
  Some of the outstanding bugs in the server are as follows:
  > Only minimal support for Wild Cards is provided (ie only for NLST command to facilitate 
    mget *.xxx from MS-DOS FTP Client)

  > When the number of users connecting to the Server reach around 20 - 30,
    the Util.init() method, hangs. This problem does not let further users to get
    authenticated. This persists until the Server is restarted.
    ( the above problem may be due to the fact that there is no API available to release 
    the socket created by Util.init())

  > When two concurrent users are in the same directory, if one uploads a file to the server,
    the file does not appear in the file listing of the other user.
    A similar problem is faced during deletion of a file.

  > If login fails for repeated attempts( 3 to 5 minimum), and then the user successfully
    logs in, only  the root folders are properly listed, their child folders are not 
    returned by portal. 

  > The scalability of the server is lower than the previous build.