Hi Gary, Using web server software is a little like using Windows file sharing except that the files being served are read only. When a client lets say web browser, requests a file the server just delivers the file back to the browser. In terms of standard files in the htdocs folder it is a one way trip, files can't be modified and files can't be themselves uploaded.
The Apache webserver as well as other web servers, treat the cgi-bin folder as a place where executable scripts can be located. The scripts in this folder generally cannot be read by the client (unless you misconfigure it), but rather called up as executables by the web server software. Within these scripts you ca put commands, that can allow files to be created, edited deleted etc, so for read write access of sort you need to write scripts to do it. You can run the tutorial files and web server on your local machine without needing it to be accessible from a network. By default though unless you have a firewall, then normally these files will be accessible from the network. If the htdocs folder only contains files which can be publicly viewed there is not really too much of a security problem. When you have everything on the local machine and access the site using http://localhost then you can just copy the files from you machine just like you would any other folder, there is nothing really magical about it. If you are working on your own network, eg you have two P, one with the client, and the other with the web server, then you will need to make some arrangement for copying the files int the foler. I simply use a Windows (or Samba) share. If you are working on the internet with a commercial webhost, then you will not be able to set up Windows shares, so you need some other mechanism, for uploading files into the htdocs or cgi-bin folders. Often this is accomplished by setting up an FTP server in addition to the web server. In IIS for instance you can set up the FTP server with the same software. The tutorial is more about showing how to make DP work through a browser than going into the intricacies of commercial webhosting etc. The tutorial and the work based on it would be ideal for either a local machine or your internal network, where you can upload files just by copying via shares. The public web server is just an extension of the ideas. So simply, for the tutorial all you will need to upload files is Windows explorer to copy files, or to set up Windows shares to copy files. You do not need any scripts or POSTs for this Regards Brian -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gary_Gabriel Sent: Tuesday, 19 May 2009 6:43 PM To: [email protected] Subject: Re: [Dataperf] DP Web again Hi Brian In working with DPWeb there are a couple of questions- > PS, I do use a lot of the CPAN modules, such as CGI.pm. CGI::Session.pm, > File::Temp, XML::XSLT etc, can these be added to TinyPerl. > > A general question to the use of the Apache Web Server and ensuring it's integrity as Localhost. 1) To ensure server integrity and operation do scripts have to be uploaded through POST to htdocs? -or can they simply be copied into htdocs? 2) What about html pages to display? Do they have to be uploaded through POST to htdocs? or- can they be copied into htdocs? 3) Can you recommend a suitable POST, Get and file upload script to upload and get pages, or documents? What else is important to consider to ensure reliable operation? I've been playing with DpWeb and it's nice. Thanks- Gary _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
