Re: perl5.6 (was: Shared variables, inner subs and our)

2001-03-17 Thread Bogomolnyi Constantin

Hi ,

You should probably try 5.7.0 witch is much more stable than 5.6.0 (you
should not try unicode stuff , whitch is quite buggy)

I use 5.7.0  on all my production servers without any problems .

Best
- Original Message -
From: "Wim Kerkhoff" [EMAIL PROTECTED]
To: "modperl" [EMAIL PROTECTED]
Sent: Saturday, March 17, 2001 6:20 AM
Subject: Re: perl5.6 (was: Shared variables, inner subs and "our")


 Stas Bekman wrote:

  our() and other perl5.6 new APIs are too early to be endorsed, as 5.6 is
  not yet considered as a stable version for mod_perl production sites,
  therefore the guide barely touches on it.

 Would you recommend the use of perl5.6 with mod_perl?  What you are
 saying is making me queasy.

 I'm asking because I've been having bad luck with Apache::Session and
 some other modules in some mod_perl aware applications. Things aren't
 comming out the data source properly, things are hanging, things aren't
 locking/unlocking properly, etc. It could well be that the applications
 I'm working with aren't using Sessions, Tie::Cache, etc properly. I may
 downgrade to perl5.005 and give that a whirl...

 --

 Regards,

 Wim Kerkhoff





Re: perl5.6 (was: Shared variables, inner subs and our)

2001-03-17 Thread Dave Rolsky

On Fri, 16 Mar 2001, Bogomolnyi Constantin wrote:

 You should probably try 5.7.0 witch is much more stable than 5.6.0 (you
 should not try unicode stuff , whitch is quite buggy)

 I use 5.7.0  on all my production servers without any problems .

5.7.0 may have fixed some of the bugs of 5.6.0 but it is a dev release
(anything where the subversion is odd is a dev release).  I don't think
anyone working on the Perl core would recommend the use of a dev release
in production unless you absolutely need a piece of functionality present
in that particular dev release.

I'd suggest using 5.00503 until 5.6.1 comes out, which should fix lots of
bugs.


-dave

/*==
www.urth.org
We await the New Sun
==*/




[ANNOUNCE] Cache-Cache-0.04

2001-03-17 Thread DeWitt Clinton

Summary:

  The Perl Cache package provides Cache::Cache, a generic interface
  for creating persistent data stores.  This interface is implemented
  by the Cache::MemoryCache, Cache::SharedMemoryCache, Cache::FileCache, 
  Cache::SizeAwareFileCache, Cache::SizeAwareMemoryCache, and 
  Cache::SizeAwareSharedMemoryCache classes.  This work replaces 
  File::Cache and IPC::Cache.

Release Notes:

  This release offers two new classes, the SizeAwareMemoryCache 
  and the SizeAwareSharedMemoryCache, replaces the Data::Dumper 
  persistence mechanism with Storable, and adds a new 
  SizeAwareCache interface, plus some small bug fixes. 

Project Homepage:

  http://sourceforge.net/projects/perl-cache/


Tar/GZ:

  http://ftp1.sourceforge.net/perl-cache/Cache-Cache-0.04.tar.gz


Changelog:

  http://sourceforge.net/project/shownotes.php?release_id=27594


CVS tree (cvsweb):

  http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi?cvsroot=perl-cache



The following is the Cache-Cache-0.04 README file:


Copyright (C) 2001 DeWitt Clinton  All Rights Reserved
 
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation; either version 1, or (at your option)
   any later version.
  
   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.
   
   You should have received a copy of the GNU General Public License
   along with this program; if not, write to the Free Software
   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.


NAME

  Cache::Cache


DESCRIPTION

  The Perl Cache package provides Cache::Cache, a generic interface
  for creating persistent data stores.  This interface is implemented
  by the Cache::MemoryCache, Cache::SharedMemoryCache, Cache::FileCache, 
  Cache::SizeAwareFileCache, Cache::SizeAwareMemoryCache, and 
  Cache::SizeAwareSharedMemoryCache classes.  This work replaces 
  File::Cache and IPC::Cache.


REQUIREMENTS

  Digest::MD5
  File::Spec
  File::Path
  IPC::Shareable
  Storable

INSTALLATION

  perl Makefile.PL
  make
  make test
  make install


USAGE

  First, choose the best type of cache implementation for your needs.
  The simplest cache is the MemoryCache, which is suitable for
  applications that are serving multiple sequential requests, and
  which to avoid making redundant expensive queries, such as an
  Apache/mod_perl application talking to a database.  If you wish to
  share that data between processes, then perhaps the
  SharedMemoryCache is appropriate, although its behavior is tightly
  bound to the underlying IPC mechanism, which varies from system to
  system, and is unsuitable for large objects or large numbers of
  objects.  When the SharedMemoryCache is not acceptable, then
  FileCache offers all of the same functionality with similar
  performance metrics, and it is not limited in terms of the number of
  objects or their size.  If you wish to maintain a strict limit on
  the size of a file system based cache, then the SizeAwareFileCache
  is the way to go.  Similarly, the SizeAwareMemoryCache and the
  SizeAwareSharedMemoryCache add size management functionality
  to the MemoryCache and SharedMemoryCache classes respectively.
 
  Using a cache is simple.  Here is some sample code for instantiating
  and using a MemoryCache:

use Cache::Cache qw( $EXPIRES_NEVER $EXPIRES_NOW );
use Cache::MemoryCache;

my $options_hash_ref = { 'default_expires_in' = '10 seconds' };

my $cache = new Cache::MemoryCache( $options_hash_ref );

my $expires_in = '10 minutes';

$cache-set( 'Key', 'Value', $expires_in );

# if the next line is called within 10 minutes, then this 
# will return the cache value

my $value = $cache-get( 'Key' );

  Please refer to the perldoc for Cache::Cache and the related
  implementations for complete documentation.


SEE ALSO

  File::Cache and IPC::Cache


AUTHOR

  Original author: DeWitt Clinton [EMAIL PROTECTED]

  Last author: $Author: dclinton $

  Copyright (C) 2001 DeWitt Clinton





RE: enable normal SSI for output of mod_perl script

2001-03-17 Thread Geoffrey Young



-Original Message-
From: Ken Williams
To: 'Surat Singh Bhati'
Cc: [EMAIL PROTECTED]
Sent: 3/17/01 12:42 PM
Subject: RE: enable normal SSI for output of mod_perl script

[EMAIL PROTECTED] (Geoffrey Young) wrote:
Surat Singh Bhati [mailto:[EMAIL PROTECTED]]
 Hi,
 
 I want to filter/process some files using my own 
 handler as:
 
 Location /foo
SetHandler  perl-script
PerlHandler Apache::Myprocessing
 /Location
 
 Now, beofre sending the output of above handler to browser, I want
 to process it as normal server-parsed (i. e. apache should search for
 the SSI tags like !--#exec cgi="/abc.cgi"-- , process them, and 
 serve the final output to the browser.

well, you can almost do this with Apache::SSI and Apache::Filter, but
Apache::SSI can't filter #exec or #include tags.

That won't be a problem in this case, since the SSI tags are the last
thing to happen before the page is sent to the browser.  Just wanted to
make sure it was clear that Apache::SSI does support "#exec cgi" and
#include, it's just that Apache::Filter can't capture that output and
let someone else filter it.  Note that "#exec cmd" is fine.

right - sorry I wasn't clear.  I mistakenly thought he wanted to filter SSI
- MyProcessing and just wanted to warn him about using those two tags in
the middle of the chain...

my appologies...

--Geoff



undefined symbol: PL_dowarn

2001-03-17 Thread Anthony Baratta

Howdy...

I've been searching high and low for answer to this conundrum. I've found 
quite a few references to the problem, but no helpful answers so far.

I am running:

RedHat 5.2,
Linux Kernel 2.2.18 #2,
Perl 5.00502, (complied on the box replacing the default install)
(I also have run the H2PH converter, but might have missed an include 
directory.)
mod_perl (via DSO) version 1.25
gcc version 2.7.2.3
(I do not have embed perl installed.)

I've used CPAN to install the latest and greatest Bundle::DBI as well as 
Bundle::Apache.

I'm trying to run mod_perl as a DSO under Apache 1.3.14. I can successfully 
run Perl CGI scripts that use DBI.

Here is the error message:

Syntax error on line 1226 of /web/apache/conf/httpd.conf:
Can't load '/usr/lib/perl5/site_perl/5.005/i686-linux/auto/DBI/DBI.so'
for module DBI:
/usr/lib/perl5/site_perl/5.005/i686-linux/auto/DBI/DBI.so:
undefined symbol: PL_dowarn at
/usr/lib/perl5/5.00502/i686-linux/DynaLoader.pm line 168.

at /usr/lib/perl5/site_perl/5.005/i686-linux/DBI.pm line 182
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.005/i686-linux/DBI.pm line 182.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.005/Apache/DBI.pm line 4.

What other info might anyone need to help me solve this? Recommendations 
and ideas appreciated.
---
Anthony Baratta
President
Keyboard Jockeys




cvs commit: modperl-2.0/xs/maps modperl_functions.map apache_functions.map

2001-03-17 Thread dougm

dougm   01/03/17 09:33:03

  Modified:xs/maps  apache_functions.map
  Added:   xs/maps  modperl_functions.map
  Log:
  move modperl specific functions into their own .map file
  
  Revision  ChangesPath
  1.6   +0 -18 modperl-2.0/xs/maps/apache_functions.map
  
  Index: apache_functions.map
  ===
  RCS file: /home/cvs/modperl-2.0/xs/maps/apache_functions.map,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- apache_functions.map  2001/03/17 06:03:38 1.5
  +++ apache_functions.map  2001/03/17 17:33:03 1.6
  @@ -44,15 +44,6 @@
   !ap_content_type_tolower
ap_get_status_line
ap_is_initial_req
  - mpxs_Apache__RequestRec_push_handlers
  - mpxs_Apache__RequestRec_set_handlers
  - mpxs_Apache__RequestRec_get_handlers
  -
  - #protocol module helpers
  - mpxs_Apache__RequestRec_location_merge
  - mpxs_Apache__RequestRec_set_basic_credentials
  -PACKAGE=Apache::RequestRec
  - mpxs_Apache__RequestRec_new
   
   #MODULE=Apache::RequestConfig
ap_document_root
  @@ -89,8 +80,6 @@
ap_rvputs | mpxs_ | ... | puts
   -ap_vrprintf
   
  - mpxs_Apache__RequestRec_TIEHANDLE
  -
   MODULE=Apache::Response   PACKAGE=guess
ap_make_etag
ap_set_content_length
  @@ -137,9 +126,6 @@
ap_construct_server
ap_construct_url | | r,uri,p
ap_error_log2stderr
  - mpxs_Apache__Server_push_handlers
  - mpxs_Apache__Server_set_handlers
  - mpxs_Apache__Server_get_handlers
   
   #MODULE=Apache::ServerConfig
ap_exists_config_define
  @@ -188,10 +174,6 @@
   MODULE=Apache::Filter PACKAGE=Apache::RequestRec
   ap_filter_t *:DEFINE_add_output_filter | | \
 request_rec *:r, const char *:name, void *:ctx
  -
  -PACKAGE=Apache::OutputFilter
  - mpxs_Apache__OutputFilter_print | | ...
  - mpxs_Apache__OutputFilter_read  | | ...
   
   PACKAGE=guess
   ~ap_add_output_filter
  
  
  
  1.1  modperl-2.0/xs/maps/modperl_functions.map
  
  Index: modperl_functions.map
  ===
  #modperl specfic functions
  
  MODULE=Apache::RequestUtil   PACKAGE=guess
   mpxs_Apache__RequestRec_push_handlers
   mpxs_Apache__RequestRec_set_handlers
   mpxs_Apache__RequestRec_get_handlers
  
   #protocol module helpers
   mpxs_Apache__RequestRec_location_merge
   mpxs_Apache__RequestRec_set_basic_credentials
  PACKAGE=Apache::RequestRec
   mpxs_Apache__RequestRec_new
  
  MODULE=Apache::RequestIO   PACKAGE=Apache::RequestRec
   mpxs_Apache__RequestRec_TIEHANDLE
  
  MODULE=Apache::ServerUtil   PACKAGE=guess
   mpxs_Apache__Server_push_handlers
   mpxs_Apache__Server_set_handlers
   mpxs_Apache__Server_get_handlers
  
  MODULE=Apache::Filter   PACKAGE=Apache::OutputFilter
   mpxs_Apache__OutputFilter_print | | ...
   mpxs_Apache__OutputFilter_read  | | ...