modperl::global(3pm) [debian man page]

libapache2-mod-perl2-2.0.7::docs::api::ModPerl::Global(3User Contributed Perl Documentalibapache2-mod-perl2-2.0.7::docs::api::ModPerl::Global(3pm)

NAME

       ModPerl::Global -- Perl API for manipulating special Perl lists

Synopsis
	 use ModPerl::Global ();
	 my $package = 'MyApache2::Package';

	 # make the END blocks of this package special
	 ModPerl::Global::special_list_register(END => $package);

	 # Execute all encoutered END blocks from this package now
	 ModPerl::Global::special_list_call(	END => $package);

	 # delete the list of END blocks
	 ModPerl::Global::special_list_clear(	END => $package);

Description
       "ModPerl::Global" provides an API to manipulate special perl lists. At the moment only the "END" blocks list is supported.

       This API allows you to change the normal Perl behavior, and execute special lists when you need to.

       For example "ModPerl::RegistryCooker" uses it to run "END" blocks in the scripts at the end of each request.

       Before loading a module containing package $package, you need to register it, so the special blocks will be intercepted by mod_perl and not
       given to Perl. "special_list_register" does that. Later on when you want to execute the special blocks, "special_list_call" should be
       called. Unless you want to call the list more than once, clear the list with "special_list_clear".

API

       "ModPerl::Global" provides the following methods:

   "special_list_call"
       Call the special list

	 $ok = special_list_call($key => $package);

       arg1: $key ( string )
	   The name of the special list. At the moment only 'END' is supported.

       arg2: $package ( string )
	   what package to special list is for

       ret: $ok ( boolean )
	   true value if $key is known, false otherwise.

       since: 2.0.00

   "special_list_clear"
       Clear the special list

	 $ok = special_list_clear($key => $package);

       arg1: $key ( string )
	   The name of the special list. At the moment only 'END' is supported.

       arg2: $package ( string )
	   what package to special list is for

       ret: $ok ( boolean )
	   true value if $key is known, false otherwise.

       since: 2.0.00

   "special_list_register"
       Register the special list

	 $ok = special_list_call($key => $package);

       arg1: $key ( string )
	   The name of the special list. At the moment only 'END' is supported.

       arg2: $package ( string )
	   what package to special list is for

       ret: $ok ( boolean )
	   true value if $key is known, false otherwise.

       since: 2.0.00

       Notice that you need to register the package before it is loaded. If you register it after, Perl has already compiled the "END" blocks and
       there are no longer under your control.

See Also
       mod_perl 2.0 documentation.

Copyright
       mod_perl 2.0 and its core modules are copyrighted under The Apache Software License, Version 2.0.

Authors
       The mod_perl development team and numerous contributors.

perl v5.14.2							    2011-02-08	       libapache2-mod-perl2-2.0.7::docs::api::ModPerl::Global(3pm)

libapache2-mod-perl2-2.0.7::docs::api::ModPerl::Util(3pmUser Contributed Perl Documentatilibapache2-mod-perl2-2.0.7::docs::api::ModPerl::Util(3pm)

NAME

       ModPerl::Util - Helper mod_perl Functions

Synopsis
	 use ModPerl::Util;

	 # e.g. PerlResponseHandler
	 $callback = ModPerl::Util::current_callback;

	 # exit w/o killing the interpreter
	 ModPerl::Util::exit();

	 # untaint a string (do not use it! see the doc)
	 ModPerl::Util::untaint($string);

	 # removes a stash (.so, %INC{$stash}, etc.) as best as it can
	 ModPerl::Util::unload_package($stash);

	 # current perl's address (0x92ac760 or 0x0 under non-threaded perl)
	 ModPerl::Util::current_perl_id();

Description
       "ModPerl::Util" provides mod_perl utilities API.

API

       "ModPerl::Util" provides the following functions and/or methods:

   "current_callback"
       Returns the currently running callback name, e.g. 'PerlResponseHandler'.

	 $callback = ModPerl::Util::current_callback();

       ret: $callback ( string )
       since: 2.0.00

   "current_perl_id"
       Return the memory address of the perl interpreter

	 $perl_id = ModPerl::Util::current_perl_id();

       ret: $perl_id ( string )
	   Under threaded perl returns something like: 0x92ac760

	   Under non-thread perl returns 0x0

       since: 2.0.00

       Mainly useful for debugging applications running under threaded-perl.

   "exit"
       Terminate the request, but not the current process (or not the current Perl interpreter with threaded mpms).

	 ModPerl::Util::exit($status);

       opt arg1: $status ( integer )
	   The exit status, which as of this writing is ignored. (it's accepted to be compatible with the core "exit" function.)

       ret: no return value
       since: 2.0.00

       Normally you will use the plain "exit()" in your code. You don't need to use "ModPerl::Util::exit" explicitly, since mod_perl overrides
       "exit()" by setting "CORE::GLOBAL::exit" to "ModPerl::Util::exit". Only if you redefine "CORE::GLOBAL::exit" once mod_perl is running, you
       may want to use this function.

       The original "exit()" is still available via "CORE::exit()".

       "ModPerl::Util::exit" is implemented as a special "die()" call, therefore if you call it inside "eval BLOCK" or "eval "STRING"", while an
       exception is being thrown, it is caught by "eval". For example:

	 exit;
	 print "Still running";

       will not print anything. But:

	 eval {
	    exit;
	 }
	 print "Still running";

       will print Still running. So you either need to check whether the exception is specific to "exit" and call "exit()" again:

	 use ModPerl::Const -compile => 'EXIT';
	 eval {
	    exit;
	 }
	 exit if $@ && ref $@ eq 'APR::Error' && $@ == ModPerl::EXIT;
	 print "Still running";

       or use "CORE::exit()":

	 eval {
	    CORE::exit;
	 }
	 print "Still running";

       and nothing will be printed. The problem with the latter is the current process (or a Perl Interpreter) will be killed; something that you
       really want to avoid under mod_perl.

   "unload_package"
       Unloads a stash from the current Perl interpreter in the safest way possible.

	 ModPerl::Util::unload_package($stash);

       arg1: $stash ( string )
	   The Perl stash to unload. e.g. "MyApache2::MyData".

       ret: no return value
       since: 2.0.00

       Unloading a Perl stash (package) is a complicated business. This function tries very hard to do the right thing. After calling this
       function, it should be safe to "use()" a new version of the module that loads the wiped package.

       References to stash elements (functions, variables, etc.) taken from outside the unloaded package will still be valid.

       This function may wipe off things loaded by other modules, if the latter have inserted things into the $stash it was told to unload.

       If a stash had a corresponding XS shared object (.so) loaded it will be unloaded as well.

       If the stash had a corresponding entry in %INC, it will be removed from there.

       "unload_package()" takes care to leave sub-stashes intact while deleting the requested stash. So for example if "CGI" and "CGI::Carp" are
       loaded, calling "unload_package('CGI')" won't affect "CGI::Carp".

   "untaint"
       Untaint the variable, by turning its tainted SV flag off (used internally).

	 ModPerl::Util::untaint($tainted_var);

       arg1: $tainted_var (scalar)
       ret: no return value
	   $tainted_var is untainted.

       since: 2.0.00

       Do not use this function unless you know what you are doing. To learn how to properly untaint variables refer to the perlsec manpage.

See Also
       mod_perl 2.0 documentation.

Copyright
       mod_perl 2.0 and its core modules are copyrighted under The Apache Software License, Version 2.0.

Authors
       The mod_perl development team and numerous contributors.

perl v5.14.2							    2011-02-08		 libapache2-mod-perl2-2.0.7::docs::api::ModPerl::Util(3pm)