ANNOUNCE: HTML::Mason 0.88

[Jonathan Swartz <sw...@pobox.com>]

The URL

    http://www.masonhq.com/download/HTML-Mason-0.88.tar.gz

has entered CPAN as

  file: $CPAN/authors/id/J/JS/JSWARTZ/HTML-Mason-0.88.tar.gz
  size: 261334 bytes
   md5: bee596df529e4b405c223d5bdfb8bd3a

Mason is a component-based web site development system with caching,
debugging, and previewing facilities.  Check out http://www.masonhq.com
for more information.

Dave Rolsky (autarch@urth.org) was the primary developer on this release.

Changes in 0.88:

  - Fixed broken Parser postprocessor code (broken since 0.85).  Added
  tests for this code path as well as the preprocessor feature.
  (Reported by Tim Bishop).
  - Replaced lots of simple accessors with new HTML::Mason::MethodMaker
  (which just makes simple read-only and read-write accessor methods).
  - Removed all direct hash key access from one object into another.
  - Removed all unneeded uses of Exporter in various modules.
  - Added warning about using mod_perl as a DSO to README file.
  - Added 'cgi_object' method to HTML::Mason::Request::ApacheHandler.
  This method returns the CGI object Mason uses internally (unless
  you're using Apache::Request instead in which case its a fatal error).
  Added documentation for this. (suggested by many people).
  - Squashed warning in assignment to %ARGS in component sub body.
  - Fixed call_method and scall_method to take arbitrary list of args
  instead of hash.
  - Fixed expression escape flags to allow arbitrary following
  whitespace.  (reported by Mikhail Zabaluev)
  - Added FAQ on how to handle file uploads.
  - $m->cache returns the value stored on a successful store action.
  - Reduced memory usage by removing unneeded uses of various modules.
  On my box I see about a 500k or so reduction in memory use (Dave).
  - Removed all uses of the IO::* modules.
  - Mason seems to be working under a mod_perl DSO, at least under
  mod_perl 1.24 and Apache 1.3.12.  This probably has nothing to do with
  Mason but the very adventurous are encouraged to experiment with a
  mod_perl DSO and report back to the mason list.

Re: Apache::DBI Wisdom Sought

[Chris Winters <cw...@intes.net>]

* Mark D Wolinski (mark@mrmark.com) [000831 11:24]:
> Hi all,
> 
> You'll pardon me a little, I hope for this message does tend to lap over out
> of ModPerl, but if it'll make you feel at ease,  I shall only expect wisdom
> on the modperl side.
> 
> I run a service of free message boards where users can create their own
> message boards.  Currently and in the past, I have used BerkeleyDB to store
> everything.
> 
> I have decided to move towards mySQL and run under ModPerl.
> 
> My current plan is to have one DB which stores everyones settings, etc in
> tables.
> 
> Then I was going to create a database for each message board.
> 
> Under ModPerl, I was going to utilize Apache::DBI to create a persistent
> connection to the main DB.  However, how will this affect the connections
> being made to individual DBs?  I have a nagging feeling that they'll connect
> until mySQL reaches it's concurrent connection limit then stop being able to
> connect to service since it would be filled with persistent connections of
> the first 150 (or so) forums accessed.
> 
> Am I correct in my feelings on that?

You could always connect to the 'mysql' database in your connection
string, and then 'use' the database you'd like once you get the
connection back:

 my $dbh = DBI->connect( 'DBI:mysql:database=mysql', 'user', 'pass',
                         { RaiseError => 1 } )
               || die $DBI::errstr;
 $dbh->do( "use $the_proper_database" );

 ... continue ...

I use this all the time, no problems. 

Chris

-- 
Chris Winters
Senior Internet Developer    intes.net
cwinters@intes.net           http://www.intes.net/
Integrated hardware/software solutions to make the Internet work for you.

Apache::DBI Wisdom Sought

[Mark D Wolinski <ma...@mrmark.com>]

Hi all,

You'll pardon me a little, I hope for this message does tend to lap over out
of ModPerl, but if it'll make you feel at ease,  I shall only expect wisdom
on the modperl side.

I run a service of free message boards where users can create their own
message boards.  Currently and in the past, I have used BerkeleyDB to store
everything.

I have decided to move towards mySQL and run under ModPerl.

My current plan is to have one DB which stores everyones settings, etc in
tables.

Then I was going to create a database for each message board.

Under ModPerl, I was going to utilize Apache::DBI to create a persistent
connection to the main DB.  However, how will this affect the connections
being made to individual DBs?  I have a nagging feeling that they'll connect
until mySQL reaches it's concurrent connection limit then stop being able to
connect to service since it would be filled with persistent connections of
the first 150 (or so) forums accessed.

Am I correct in my feelings on that?

Secondly, you may be asking why I don't just store the messages in a single
table in the master database.  My thoughts on that are that when a message
is posted, I create a list of the thread and write those numbers to the
messages to allow quicker retrieval when the message list looked at.  When I
do this, I write lock the DB to prevent concurrent posts from messing up the
threading of another post.  On that point, I may well be over zealously
protective and while this paragraph is so far off topic I would love your
thoughts on that issue, but would understand if shall pass it up to respond
only to the modperl portion of this message.  And I can seek council via the
mysql lists as well on this issue.

Much thanks...

Mark W