You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl-cvs@perl.apache.org by ri...@hyperreal.org on 1999/11/04 07:49:42 UTC

cvs commit: modperl-site/embperl Changes.pod.1.html Embperl.pod.1.html Embperl.pod.11.html Embperl.pod.5.html Embperl.pod.6.html Embperl.pod.cont.html index.html

richter     99/11/03 22:49:41

  Modified:    embperl  Changes.pod.1.html Embperl.pod.1.html
                        Embperl.pod.11.html Embperl.pod.5.html
                        Embperl.pod.6.html Embperl.pod.cont.html index.html
  Log:
  Embperl Webpages - Changes
  
  Revision  Changes    Path
  1.110     +1 -1      modperl-site/embperl/Changes.pod.1.html
  
  Index: Changes.pod.1.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Changes.pod.1.html,v
  retrieving revision 1.109
  retrieving revision 1.110
  diff -u -r1.109 -r1.110
  --- Changes.pod.1.html	1999/11/04 06:34:56	1.109
  +++ Changes.pod.1.html	1999/11/04 06:49:28	1.110
  @@ -28,7 +28,7 @@
        from Jason Holt.
      - Changed access to addtional upload fileinfo. The old syntax
        (${${$fdat{<name_of_field>}}}) isn't available anymore, because
  -     it doesn't work with filenames that are not a vaild per
  +     it doesn't work with filenames that are not a vaild perl
        variable name. Now there is a second field which start with a
        dash that's holds a hash ref to the file info. Spotted by 
        Huang-Ming Pan.
  
  
  
  1.12      +13 -6     modperl-site/embperl/Embperl.pod.1.html
  
  Index: Embperl.pod.1.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Embperl.pod.1.html,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- Embperl.pod.1.html	1999/11/01 08:26:28	1.11
  +++ Embperl.pod.1.html	1999/11/04 06:49:29	1.12
  @@ -20,6 +20,7 @@
   
   		<LI><A href="Embperl.pod.1.html#Offline">Offline</A>
   		<LI><A href="Embperl.pod.1.html#As_a_CGI_script">As a CGI script</A>
  +		<LI><A href="Embperl.pod.1.html#From_mod_perl_Apache_httpd_">From mod_perl (Apache httpd)</A>
   		<LI><A href="Embperl.pod.1.html#By_calling_HTML_Embperl_Execut">By calling HTML::Embperl::Execute (\%param)</A>
   		<LI><A href="Embperl.pod.1.html#Helper_functions_for_Execute">Helper functions for Execute</A>
   		<LI><A href="Embperl.pod.1.html#EXAMPLES_for_Execute_">EXAMPLES for Execute:</A>
  @@ -131,11 +132,13 @@
   script!
   
   <P>
  -<STRONG>NOTE 2</STRONG>: CGI Scripts are not so secure. You should consider using <EM>EMBPERL_ALLOW</EM>
  -to restrict the access to the rights documents. =head2 From mod_perl
  -(Apache httpd)
  +<STRONG>NOTE 2</STRONG>: CGI Scripts are not so secure. You should consider using <EM>EMBPERL_ALLOW</EM>
  +to restrict the access to the rights documents.
   
   <P>
  +<HR>
  +<H2><img src="sq.gif" width="16" height="16" alt="-"> <A NAME="From_mod_perl_Apache_httpd_">From mod_perl (Apache httpd)</A></H2>
  +<P>
   This works like the CGI-Script, but with the advantage that the script is
   compiled only once at server startup, where other one-time actions (such as
   opening files and databases) can take place. This will drastically reduce
  @@ -193,9 +196,8 @@
   so you can view the log file with your browser!
   
   <P>
  -<STRONG>NOTE</STRONG>: When mod_perl is compiled as loadable module (i.e. with USE_DSO) you
  -<STRONG>must not</STRONG> load Embperl at server startup time! 
  -
  +<STRONG>NOTE</STRONG>: When mod_perl is compiled as loadable module (i.e. with USE_DSO) you
  +<STRONG>must not</STRONG> load Embperl at server startup time! 
   
   <P>
   <HR>
  @@ -397,6 +399,11 @@
   <DT><STRONG><A NAME="item_cookie_expires">cookie_expires</A></STRONG><DD>
   <P>
   Same as <A href="Embperl.pod.2.html#EMBPERL_COOKIE_EXPIRES">EMBPERL_COOKIE_EXPIRES</A> (see below).
  +
  +<DT><STRONG><A NAME="item_errors">errors</A></STRONG><DD>
  +<P>
  +Takes a reference to an array. Upon return the array will contain a copy of
  +all errormessages, as long as there are any.
   
   </DL>
   <P>
  
  
  
  1.5       +3 -1      modperl-site/embperl/Embperl.pod.11.html
  
  Index: Embperl.pod.11.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Embperl.pod.11.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- Embperl.pod.11.html	1999/05/10 20:36:56	1.4
  +++ Embperl.pod.11.html	1999/11/04 06:49:30	1.5
  @@ -24,7 +24,9 @@
   should <STRONG>never</STRONG> enable <STRONG>dbgFlushOutput</STRONG>, <STRONG>dbgFlushLog</STRONG> or
   <STRONG>dbgCacheDisable</STRONG> in a production environment. More debugging options are useful for
   development where it doesn't matter if the request takes a little bit
  -longer, but on a heavily-loaded server they should be disabled.
  +longer, but on a heavily-loaded server they should be disabled. Addtionaly
  +the options <EM>optDisableChdir</EM>, <EM>optDisableHtmlScan</EM>,
  +<EM>optDisableCleanup</EM> have consequences for the performance.
   
   <P>
   Also take a look at <STRONG>mod_perl_tuning.pod</STRONG> for general ideas about performance.
  
  
  
  1.14      +8 -4      modperl-site/embperl/Embperl.pod.5.html
  
  Index: Embperl.pod.5.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Embperl.pod.5.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- Embperl.pod.5.html	1999/10/21 05:46:42	1.13
  +++ Embperl.pod.5.html	1999/11/04 06:49:30	1.14
  @@ -93,16 +93,20 @@
   filename (local filename, as it was on the browser side) and the
   informations provied by the CGI.pm uploadInfo function. To get the filename
   just print out the value of the correspondig <CODE>%fdat</CODE> entry,
  -instead of using it as a filehandle. To get the uploadInfo you must two
  -times dereference it.
  +instead of using it as a filehandle. To get the <STRONG>uploadInfo</STRONG> use the fieldname with a dash in front of it:
   
   <P>
   <PRE>  Example:
   </PRE>
   <P>
  -<PRE>  Filename:      [+ $fdat{ImageName} +] &lt;br&gt;
  -  Content-Type:  [+ ${${$fdat{ImageName}}} -&gt; {'Content-Type'} +] &lt;br&gt;
  +<PRE>  # ImageName is the NAME of the field, you must replace it with whatever 
  +  # name is given in your HTML code
  +  Filename:      [+ $fdat{ImageName} +] &lt;br&gt;
  +  Content-Type:  [+ $fdat{-ImageName} -&gt; {'Content-Type'} +] &lt;br&gt;
   </PRE>
  +<P>
  +<STRONG>NOTE:</STRONG> The way <STRONG>uploadInfos</STRONG> are accessed before 1.2b11 are not supported anymore.
  +
   <P>
   <HR>
   <H2><img src="sq.gif" width="16" height="16" alt="-"> <A NAME="_ffld">@ffld</A></H2>
  
  
  
  1.12      +17 -73    modperl-site/embperl/Embperl.pod.6.html
  
  Index: Embperl.pod.6.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Embperl.pod.6.html,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- Embperl.pod.6.html	1999/11/01 08:26:29	1.11
  +++ Embperl.pod.6.html	1999/11/04 06:49:30	1.12
  @@ -20,20 +20,18 @@
   <P>
   From 1.2b1 and higher Embperl is able to handle per user sessions for you.
   You can store any data in the <EM>%udat</EM> hash and if the same user request again an Embperl document, you will see
  -the same values in that hash again. (see <STRONG>IMPORTANT NOTE:</STRONG> below for using DBI as storage)
  +the same values in that hash again. 
   
   <P>
   From 1.2b2 and higher Embperl is able to handle per module/page persitent
   data for you. You can store any data in the <EM>%mdat</EM> hash and if any request comes to the same Embperl document, you will see
  -the same values in that hash again. (see <STRONG>IMPORTANT NOTE:</STRONG> below for <CODE>%mdat</CODE> storage)
  +the same values in that hash again. 
   
   <P>
  -To configure Embperl to do session management for you, you must have
  -installed Apache::Session (1.04 or higher) and loaded
  -Apache::Session::Embperl before you load Embperl and you must tell Embperl
  -which storage and locker classes you would like to use for Apache::Session,
  -by setting the environement variable EMBPERL_SESSION_CLASSES. You may have
  -a <STRONG>startup.pl</STRONG> for your httpd which looks like this:
  +To configure <EM>Embperl</EM> to do session management for you, you must have installed <EM>Apache::Session</EM> (<STRONG>1.00 or higher</STRONG>) and tell Embperl which storage and locker classes you would like to use
  +for
  +<EM>Apache::Session</EM>. This is done by setting the environement variable 
  +<CODE>EMBPERL_SESSION_CLASSES</CODE>. You may have a <STRONG>startup.pl</STRONG> for your httpd which looks like this:
   
   <P>
   <PRE> BEGIN
  @@ -43,60 +41,33 @@
       } ;
   </PRE>
   <P>
  -<PRE> use Apache::Session::Embperl ;
  - use HTML::Embperl ;
  -
  -For B&lt;Solaris&gt; it's neccessary to set the C&lt;nsems&gt; Argument of SysVSemaphoreLocker
  -
  - $Apache::Session::SysVSemaphoreLocker::nsems = 16;
  +<PRE> use HTML::Embperl ;
   </PRE>
   <P>
  +For <STRONG>Solaris</STRONG> it's neccessary to set the <CODE>nsems</CODE> Argument if you use SysVSemaphoreLocker
  +
  +<P>
  +<PRE> $Apache::Session::SysVSemaphoreLocker::nsems = 16;
  +</PRE>
  +<P>
   You may also put this in the httpd/srm.conf:
   
   <P>
   <PRE> PerlSetEnv EMBPERL_SESSION_CLASSES &quot;DBIStore SysVSemaphoreLocker&quot;
    PerlSetEnv EMBPERL_SESSION_ARGS &quot;DataSource=dbi:mysql:session UserName=test&quot;
  - PerlModule Apache::Session::Embperl ;
    PerlModule HTML::Embperl ;
   </PRE>
   <P>
   <CODE>EMBPERL_SESSION_ARGS</CODE> is a space separated list of name/value pairs, which gives additional
   arguments for Apache::Session classes.
   
  -<P>
  -<STRONG>NOTE:</STRONG> Apache::Session 1.04 needs a totaly different setup then Apache::Session
  -0.17
  -
  -<P>
  -Older versions of <EM>Embperl</EM> need <EM>Apache::Session</EM> 0.17. You can use it like the following, 
  -<STRONG>but you should as soon as possible upgrade to newer Apache::Session an Embperl version</STRONG>:
  -
  -<P>
  -<PRE> $ENV{SESSION_FILE_DIRECTORY}='/tmp/sessions' ;
  - $ENV{EMBPERL_SESSION_CLASS}='File' ;
  - use Apache::Session::File ;
  - use HTML::Embperl ;
  -</PRE>
  -<P>
  -<PRE> 1 ;
  -</PRE>
  -<P>
  -or put it in the httpd/srm.conf like this
  -
   <P>
  -<PRE> PerlSetEnv SESSION_FILE_DIRECTORY /tmp/sessions
  - PerlSetEnv EMBPERL_SESSION_CLASS  File
  - PerlModule Apache::Session::File 
  - PerlModule HTML::Embperl 
  -</PRE>
  -<P>
  -NOTE 1: You can use all the environement variables recognized by
  -Apache::Session to configure it.
  +<STRONG>NOTE:</STRONG> The above configuration works only with <EM>Embperl</EM> 1.2b11 or above. The way
  +<EM>Apache::Session</EM> was used in earlier versions still works, but I have removed the
  +documentation to avoid confusion. Changes are, that you don't need to load
  +<EM>Apache::Session</EM> anymore on your own and that <EM>Apache::Session 1.00</EM> takes totaly different arguments then <EM>Apache::Session 0.17</EM>.
   
   <P>
  -NOTE 2: Do not use SetEnv, use PerlSetEnv instead in your httpd/srm.conf
  -
  -<P>
   Now you are able to use the <CODE>%udat</CODE> and <CODE>%mdat</CODE> hashs
   for your user/module sessions. As long as you don't touch
   <CODE>%udat</CODE> or <CODE>%mdat</CODE> Embperl will not create any
  @@ -107,33 +78,6 @@
   store data to <CODE>%mdat</CODE> Embperl will store the data via
   Apache::Session and retrieves it when the next request comes to the same
   page.
  -
  -<P>
  -<STRONG>IMPORTANT NOTE for DBI and %mdat usage and Apache::Session <STRONG>0.17</STRONG> <STRONG>not</STRONG> valid for 1.01!:</STRONG> The storage of <CODE>%mdat</CODE> requires a proper serialization of the
  -access. Apache::Session (version 0.17) is not able to provide this. While
  -this is no problem when using the Apache::Session::Win32 as storage class,
  -this will be a problem for all other storage medias. The Embperl
  -distribution comes with a patch for that purpose. This works only for
  -Apache::Session::DBI, so if you like to use %mdat, currently you can only
  -do so when using Apache::Session::Win32 or Apache::Session::DBI as storage
  -class.
  -
  -<P>
  -To use <STRONG>Apache::Session::DBI</STRONG> together with Embperl you need to use <STRONG>Apache::Session::epDBI</STRONG> (which comes with Embperl) instead. Apache::Session::epDBI has two
  -enhancements over standard Apache::Session::DBI. 1.) It serialzies all
  -requests. 2.) It corrects a problems which will lead locks to not releases
  -with normal Apache::Session::DBI. So your configuration for storing session
  -data via DBI might look like the following:
  -
  -<P>
  -<PRE> PerlSetEnv SESSION_DBI_DATASOURCE dbi:mysql:session
  - PerlSetEnv EMBPERL_SESSION_CLASS  epDBI
  - PerlModule Apache::Session::epDBI 
  - PerlModule HTML::Embperl 
  -</PRE>
  -<P>
  -While usage of <STRONG>Apache::Session::File</STRONG> works ok for the <CODE>%udat</CODE> storage, it does <STRONG>not</STRONG> work for the <CODE>%mdat</CODE> storage, because of the not working locking
  -and serialization. 
   
   <p>[<a href="index.html">HOME</a>]&nbsp;&nbsp; [<a href="Embperl.pod.cont.html">CONTENT</a>]&nbsp;&nbsp; [<a href="Embperl.pod.5.html">PREV (Predefined variables)</a>]&nbsp;&nbsp; [<a href="Embperl.pod.7.html">NEXT ((Safe-)Namespaces and opcode restrictions)</a>]&nbsp;&nbsp; <br>
       <font color="#808080">___________________________________________________________________________________<br>
  
  
  
  1.17      +1 -1      modperl-site/embperl/Embperl.pod.cont.html
  
  Index: Embperl.pod.cont.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/Embperl.pod.cont.html,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- Embperl.pod.cont.html	1999/11/01 08:26:29	1.16
  +++ Embperl.pod.cont.html	1999/11/04 06:49:31	1.17
  @@ -33,7 +33,7 @@
   
   		<LI><A href="Embperl.pod.1.html#Offline">Offline</A>
   		<LI><A href="Embperl.pod.1.html#As_a_CGI_script">As a CGI script</A>
  -		<LI><A href="Embperl.pod.cont.html#From_mod_perl_Apache_httpd_">From mod_perl (Apache httpd)</A>
  +		<LI><A href="Embperl.pod.1.html#From_mod_perl_Apache_httpd_">From mod_perl (Apache httpd)</A>
   		<LI><A href="Embperl.pod.1.html#By_calling_HTML_Embperl_Execut">By calling HTML::Embperl::Execute (\%param)</A>
   		<LI><A href="Embperl.pod.1.html#Helper_functions_for_Execute">Helper functions for Execute</A>
   		<LI><A href="Embperl.pod.1.html#EXAMPLES_for_Execute_">EXAMPLES for Execute:</A>
  
  
  
  1.55      +0 -0      modperl-site/embperl/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/modperl-site/embperl/index.html,v
  retrieving revision 1.54
  retrieving revision 1.55
  diff -u -r1.54 -r1.55
  --- index.html	1999/11/04 06:34:57	1.54
  +++ index.html	1999/11/04 06:49:31	1.55
  @@ -212,7 +212,7 @@
   <blockquote>
     <p><font color="#808080">___________________________________________________________________________________<br>
     HTML::Embperl - Copyright (c) 1997-99 Gerald Richter / ECOS &lt;richter@dev.ecos.de&gt;<br>
  -  Last Update $Id: index.html,v 1.54 1999/11/04 06:34:57 richter Exp $</font></p>	
  +  Last Update $Id: index.html,v 1.55 1999/11/04 06:49:31 richter Exp $</font></p>	
   </blockquote>
   </td></tr><!--msnavigation--></table></body>
   </html>