HTTP File Attachment for WINS                      version 1.0a
by Earl Borah and Timothy Rogers
Network Connect Northwest                          http://www.ncn.com

Originally developed for Chemeketa Online BBS      http://bbs.chemek.cc.or.us




What's New in version 1.0a??

Minor documentation changes...an older README.TXT file was accidentally
included in the 1.0 version. Ooops!

We also added a TESTING.HTM file, for easier testing of the shareware version.



What's in this ZIP??

FILE:                      REQUIRED LOCATION:     ADDT'L INFO:

HTML-PROCESS MESSAGE.WCX   \wc5\                  Program file
HTML-POST.WCX              \wc5\                  Program file
ATTACH9451.EXE             CGI Directory          Program file
HTTPUPLOAD.KEY             \wc5\data\             Registration key
MESSAGE_CREATE.HTM         \wc5\http\template\    New message template
UPLOAD.HTM                 \wc5\http\template\    Upload instructions template
TESTING.HTM                \wc5\http\             Test page for SYSOP use
ABORTBUTTON.GIF            \wc5\http\images\      Abort message button
SENDBUTTON.GIF             \wc5\http\images\      Send message button
README.TXT (this file)     anywhere               This documentation
REGISTER.TXT               anywhere               Registration information



What does this program do??

Now you can allow your users to attach files to messages they send through
dynamic-HTML. The users must be using a web browser that supports HTTP Uploads
(which currently means Netscape version 2.0 or higher). I understand there is
an add-on available from Microsoft that will add this functionality to 
Microsoft Internet Explorer as well, but I have been unable to confirm it.

When your users are creating a message normally, they will see a new line
(below the "To", "Subject", "Conference",  and "Private" lines), which will
give them the option to send a file attachment. If they select Yes, then they
will be prompted to find a file on their hard drive to send. Once the file is
sent, they'll receive a confirmation message (including the name and size of
the file received) and be prompted to save their message with the file
attached.



INSTALLATION INSTRUCTIONS

First, you must copy the files above into their proper locations. At this
time, all filenames and directories are hardcoded. Make sure you put 
ATTACH9451.EXE in your CGI directory, wherever that may be (it's configured
under wcConfig, Computers).

***IMPORTANT***
You must also make a directory on your hard drive named C:\HTTPUpload -- this
is a hard-coded directory, and it must exist in that location. Future versions
of this program may allow this directory to be configurable. Only small temp
files will be placed in this directory, but it is vital to the operation of
the program. IF YOU RUN WCONLINE ON MULTIPLE COMPUTERS, EACH COMPUTER MUST
HAVE A C:\HTTPUPLOAD DIRECTORY CREATED.

You may edit the HTML pages if you like...the UPLOAD.HTM page currently
contains much important information for your users, however, so be careful
how you edit it. The MESSAGE_CREATE.HTM file should replace the one that is
currently in your template directory -- you may wish to back up the original
before you install these files. If you like, you can use the TESTING.HTM file
provided for your own testing, prior to overwriting the MESSAGE_CREATE.HTM
file.



What are the limitations??

1. Only works with web browsers that support HTTP Uploads (namely Netscape,
version 2.0 or higher).

2. In the shareware version, the only users allowed to attach files to a
message are any users with the same name as the Administrator (as defined in
wcConfig, General Info). If anyone else selects the checkbox that allows them
to attach a file to a message, then the status of the checkbox is ignored. In
the registered version, all users will be able to attach a file to their
message, provided the conference allows attachments.

3. If the user sends a message in a conference that does not allow file
attachments, the attachment field is ignored and the message is sent normally.
The user is never prompted to upload a file, but they are not notified why the
file attachment field was ignored. Better error trapping may be added in a
future version.

4. Users can only send one message with an attachment at a time. For example,
if a user has two browser windows open, starts a message with an attachment in
one window, then starts uploading the file, and works on the second message in
the second window while the file from the first window is still uploading, AND
if they say they want to send the second message (AND it is marked that they
want to attach a file to it) before the first message is posted and
acknowledgement is sent, then THEIR FIRST MESSAGE WILL BE LOST and the second
message will be posted in its place (probably with the first file attachment,
if it was uploaded successfully). So...in other words...tell your users not to
have two browser windows open at once, both of them trying to send messages
with files attached to them.

5. The C:\HTTPUpload directory is hard-coded. This may change in future
versions of this program, depending on how many registrations we receive and
the demand for this to be configurable.

6. If the user aborts the file upload, or if they decide not to send the
message, then files can be left in the c:\HTTPUpload directory. We recommend
cleaning the directory out once in a while. Delete any files at least one day
old, and you shouldn't have to worry about destroying any active temp files.
ACTIVE TEMP FILES ARE NOT LOCKED, so do not just delete all files in the
C:\HTTPUpload directory while WINS is running, or you may be deleting files
that are still needed by a user in the process of attaching a file. If you are
worried, then the absolutely safest option is to delete the entire contents of
the HTTPUpload directory when wcServer is not running.



How much does this cost??

$20 for a registration key. See REGISTER.TXT for more information.



Legal Junk:

We make no guarantees about this program, and you use it at your own risk. We
do not promise, represent, or warantee that the program will be useful for any
particular purpose, or that it will not cause damage, directly or indirectly,
to your system. If your hard drive gets thrashed, your users stop calling, and
your dog leaves you, don't blame us.