ANNOUNCE: Bricolage 1.6.5
I'm pleased to announce announce the release of Bricolage 1.6.5. This maintenance release addresses a number issues discovered since the release of version 1.6.4. Some of the more important changes include: * Previewing stories with related media that have no associated file no longer causes an error. * Switched to using DBI-connect_cached() from using our own database connection caching. This change does bump up the minimum required version of DBI to 1.18, though the latest version is always recommended. It's also the right thing to do. * Fixed issue that could cause Bric::Util::DBI to create inconsistent transaction states. * Passing an undef via the workflow__id parameters to the list() method of Story, Media, or Template really does again cause Bricolage to correctly return only those assets that are not in workflow. It wasn't as fixed in 1.6.3 as I had thought. * Vastly improved the speed of the query that lists events, and added an index to help it along, as well. * The FTP mover now properly deletes files rather than erroring out. * Users without EDIT access to the start desk in a workflow can no longer create assets in that workflow. Nor can they check out assets from the library, as there's no start desk for them to check them in to. But they can still check them out from other desks that they have EDIT access to. * Time zone issues have been fixed to be more portable. Some platforms that experienced Bricolage unexpectedly shifting cover dates and other dates and times by several hours should no longer see this problem. * Adding a new element type with the same name as an existing or deleted element type no longer causes an SQL error. For a complete list of the changes, see the changes file at: https://sourceforge.net/project/shownotes.php?release_id=183771 ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://www.kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
ANNOUNCE: Bricolage 1.6.2
I'm pleased to announce announce the release of Bricolage-Devel 1.6.2. This maintenance release addresses numerous issues discovered since the release of version 1.6.1. Some of the more important changes since 1.6.1 include: * New help pages for the destination, server, and action profiles. * Fixed issue where new output channels added to a document type element were not always actually saved as a part of that element. * Fixed installer to again work with versions of PostgreSQL prior to 7.3. * Alert types can once again be deleted from the alert type profile. * Users can now only add subelements to a story if they have at least READ permission to those subelements. * The media type profile again allows extensions to be added and removed. * Perl 5.8.0 or later is now strongly recommended for better Unicode support. * Fixed deleting an Alert Type Rule. Also fixed Editing Alert Type Recipients. * Clicking Cancel in an element no longer saves the changes in that element before going up to the parent element. * Added Localization support to widgets that were missing it. Added pt_pt localized images. * Documents are no longer distributed to deleted (deactivated) destinations. * Eliminated several error log authentication message such as No cookie found. Thes tended only to confuse users when they were just starting to use Bricolage. * Elements added with the same name as an existing, active or inactive element no longer trigger an SQL error to be displayed. * Fixed issue where adding an output channel to a document type element removed that output channel from another document type element. For a complete list of the changes, see the changes file at: http://sourceforge.net/project/shownotes.php?release_id=174317 ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
ANNOUNCE: Bricolage 1.6.1
I'm pleased to announce announce the release of Bricolage-Devel 1.6.1. This maintenance release addresses a number of issues in version 1.6.0. Some of the more important changes since 1.6.0 include: * Bricolage now works with HTML::Mason 1.20 and later. * Added Chinese (Traditional) localization. * `make clone` has been fixed and improved. * The Media Type manager works again. * Various localization improvements and fixes. * Image, Audio, and Video documents now properly show up on desks. * Fixed alerts so that alerts are once again sent to the members of groups and deleted alerts no longer appear in the UI. * The virtual FTP server no longer displays templates in subcategories of the current subcategory directory. * Fixed Element profile so that Output Channel associations can be deleted and deleted fields no longer appear in the UI. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=165152 ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
The Register Adopts Bricolage
Hi All, In yet another success for mod_perl, _The Register_ is currently building a Bricolage-powered content management infrastructure to power their site. They announcement is here: http://www.theregister.co.uk/content/31/30959.html Regards, David PS: There have been a couple of other articles about Bricolage lately, too, both indicating that analyst firms (Bloor, Jupiter) are aware of Bricolage and looking at how it fits into the IT landscape. http://www.it-director.com/article.php?articleid=10868 http://www.intranetjournal.com/articles/200305/ij_05_05_03a.html -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://kineticode.com/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
ANNOUNCE: Bricolage-Devel 1.5.2
The Bricolage team is pleased to announce the release of Bricolage-Devel 1.5.2, a release candidate for what will soon become Bricolage 1.6.0. Users of 1.5.1 are strongly encouraged to upgrade to 1.5.2, as assets have an unfortunate habit of disappearing from workflow in 1.5.1. In addition to all of the new features and bug fixes from the 1.5.0 and 1.5.1 releases, this version of the open-source content management system fixes several significant bugs and tweaks a few important features. The most significant changes include: * Out of the box, the Story Editors, Media Producers, and Template Developers groups now have READ permission to access members of the All Categories and All Elements groups, which allow them to actually create assets based on elements and within categories. * Workflow and Desk permissions are a little more sensible now. CREATE permission can be granted for the start desk in each workflow, instead of for the entire workflow. This allows a lower permission to be set on the workflow (e.g., READ), and then higher permissions on the individual desks in the workflow. * New Tuning sections have been added to Bric::DBA. * The default required length for usernames and passwords has been changed from 6 to 5. This is to make dealing with the default admin login easier. * It is once again possible to delete elements when they are not associated with any story or media asset. * Bric::Config now does its best to find a workable httpd.conf file during make test. * Previews of assets that are not checked out work again. * Workflow and desk permissions relative to the assets they contain are now restored to their previous behavior. Desks no longer simply inherit the permission granted on any of the workflows they're in. This issue was resolved by creating a new secret asset group ID for each workflow. * Assets will no longer appear to randomly disappear from workflow. For a complete list of the changes, see the changes file at http://sourceforge.net/project/shownotes.php?release_id=150544. Although this release gives every appearance of being as stable as any previous release of Bricolage, it does contain a fair bit of new code that needs to be put through the ringer. It is, however, feature complete for 1.6.0, which we expect to release in the second week of April. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
ANNOUNCE: Bricolage-Devel 1.5.1
The Bricolage team is pleased to announce the release of Bricolage-Devel 1.5.1, a beta release for what will soon become Bricolage 1.6.0. In addition to all of the new features of the 1.5.0 release, this version of the open-source content management system fixes many bugs and adds many new features and significant performance enhancements. The most significant changes include: * A new, complete internationalization and localization implementation. All messages, text buttons, JavaScript messages, and help files may be localized. Some Portuguese and Italian localization has already been done. Translators needed going forward! Thanks to Claudio Valente. * New Super Bulk Edit interface to allow story editors to edit multiple fields in a single textarea field using simple tags. Thanks to Macworld Magazine for sponsoring this development. * A further overhaul of groups and permissions. These changes make the permission checking and therefore the UI much more responsive. Thanks to Portugal Telecom for sponsoring this development. * The addition of a WebDAV distribution mover. Thanks to Joao Pedro Goncalves. * Extensive refactoring of most of the business classes, including stories, media, and templates, greatly enhancing the speed at which objects are retrieved from the database. Thanks Portugal Telecom and to Mark Jaroski. * Added a per-Apache request object cache. The prevents an object from being looked up in the database multiple times in a single request. Such was often the case during publishes, which are speeded up by this change by up to 33%. Thanks to Portugal Telecom for sponsoring this development. * Added a preview link to all subelement profiles within a story, thanks to Scott Lanning. * Switched exceptions from home-grown to using Exception::Class, thanks to Scott Lanning. * Added category group association -- including the ability to cascade membership assignments into subcategories -- to the category profile Thanks to Joao Pedro Goncalves. * The Content section of story, media, and subelement profiles now attempts to display a bit of text from the first text field in each listed subelement so that it's easier to see at a glance which subelement is which. Thanks to Joao Pedro Goncalves. * Subelement can now nest. That is, they can contain themselves. Not in a story, of course, but in the document model (element administration). * Over twenty bug fixes and a much more extensive test suite. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=148352 Although this release gives every appearance of being as stable as any previous release of Bricolage, it does contain a fair bit of new code that needs to be put through the ringer. It is, however, feature complete for 1.6.0, which we expect to release in April. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
ANNOUNCE: Bricolage-Devel 1.5.1
The Bricolage team is pleased to announce the release of Bricolage-Devel 1.5.1, a beta release for what will soon become Bricolage 1.6.0. In addition to all of the new features of the 1.5.0 release, this version of the open-source content management system fixes many bugs and adds many new features and significant performance enhancements. The most significant changes include: * A new, complete internationalization and localization implementation. All messages, text buttons, JavaScript messages, and help files may be localized. Some Portuguese and Italian localization has already been done. Translators needed going forward! Thanks to Claudio Valente. * New Super Bulk Edit interface to allow story editors to edit multiple fields in a single textarea field using simple tags. Thanks to Macworld Magazine for sponsoring this development. * A further overhaul of groups and permissions. These changes make the permission checking and therefore the UI much more responsive. Thanks to Portugal Telecom for sponsoring this development. * The addition of a WebDAV distribution mover. Thanks to Joao Pedro Goncalves. * Extensive refactoring of most of the business classes, including stories, media, and templates, greatly enhancing the speed at which objects are retrieved from the database. Thanks Portugal Telecom and to Mark Jaroski. * Added a per-Apache request object cache. The prevents an object from being looked up in the database multiple times in a single request. Such was often the case during publishes, which are speeded up by this change by up to 33%. Thanks to Portugal Telecom for sponsoring this development. * Added a preview link to all subelement profiles within a story, thanks to Scott Lanning. * Switched exceptions from home-grown to using Exception::Class, thanks to Scott Lanning. * Added category group association -- including the ability to cascade membership assignments into subcategories -- to the category profile Thanks to Joao Pedro Goncalves. * The Content section of story, media, and subelement profiles now attempts to display a bit of text from the first text field in each listed subelement so that it's easier to see at a glance which subelement is which. Thanks to Joao Pedro Goncalves. * Subelement can now nest. That is, they can contain themselves. Not in a story, of course, but in the document model (element administration). * Over twenty bug fixes and a much more extensive test suite. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=148352 Although this release gives every appearance of being as stable as any previous release of Bricolage, it does contain a fair bit of new code that needs to be put through the ringer. It is, however, feature complete for 1.6.0, which we expect to release in April. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason and HTML::Template support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: [mp1] Alternative for CHECK
On Thursday, February 20, 2003, at 10:51 PM, Stas Bekman wrote:
Why not? Use a separate module to drive the others?
package My::PostConfig;
BEGIN {
# whatever needs to be done for other modules
}
1;
startup.pl:
---
use My::PostConfig
Excellent point, and a quick experiment on my end shows that this does
do what I need. I have two different modules to be loaded for this
project, so I just make sure that one loads after the other does, and
it all works.
Thanks for the nudge, Stas, it was just what I needed.
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting knowledge in motion.[sm]
[mp1] Alternative for CHECK
Hi All, I'm writing a module that will run in Apache and has important code that needs to run after all modules have loaded but before Apache forks and starts serving requests. Since mod_perl 1.x ignores CHECK and INIT blocks, and BEGIN blocks run too early for what I'm doing, I was wondering if there's a hook in the mod_perl API where I can run some code just before before Apache forks and starts serving requests? If you must know what I'm doing, I'm looking for stuff in the symbol table. TIA! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: [mp1] Alternative for CHECK
On Thursday, February 20, 2003, at 07:04 PM, Stas Bekman wrote: PerlChildInitHandler? e.g. used by Apache::DBI to pre-connect to the db. Yeah, but I was looking for something pre-fork. Anything come to mind? Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: [mp1] Alternative for CHECK
On Thursday, February 20, 2003, at 09:41 PM, Stas Bekman wrote: startup.pl? Won't work too well in a module, I think. I have a workaround for my problem for now, but it ain't pretty. in 2.0 you have: PerlPostConfigHandler http://perl.apache.org/docs/2.0/user/handlers/ server.html#PerlPostConfigHandler Oooh, yes, that's exactly what I want. Will have to port it all when the time comes. Waiting for the mod_perl 2 momentum, now, Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Re: mod perl libapreq make test problem
On Sunday, February 16, 2003, at 09:37 AM, Lamotte Denis wrote: i think ive successfully compile apache with mod perl and mod php. i'm working on Mac osx 10.2.4 with perl 5.8.0 Did you compile the libapreq C library before compiling Apache::libapreq? See INSTALL.MacOSX in the libapreq distribution for complete details. I've also published an update to may Build Apache/mod_perl on Mac OS X article that covers this issue: http://www.macdevcenter.com/pub/a/mac/2003/02/07/libapreq_update.html HTH, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.[sm]
Bricolage on Online Tonight
Hi All, I'll be appearing on Online Tonight again tonight, at 11 pm EST / 8 pm PST. I'll be discussion Bricolage again with host David Lawrence. You can listen live online here: http://www.cnet.com/broadband/0-7227152.html And you can find an affiliate that carry the broadcast by entering your zip code here: http://www.online-tonight.com/ In related news, I posted an edited version of my last appearance on the show in RealAudio format here: http://bricolage.cc/audio/online_tonight.ram Tune in and enjoy! Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage-Devel 1.5.0
The Bricolage team is pleased to announce the release of Bricolage-Devel 1.5.0, a development release for what will eventually become Bricolage 1.6.0. In addition to all of the bug fixes included in the 1.4.6 release, this version of the 100% Perl content management system adds many new features. The most significant changes include: * A unit testing framework based on Test::Class. * Ported to HTML::Mason versions 1.16 and higher. * Output channel-specific URI format and case preferences. * Stories and media assets can now select which output channels to be published to on a per-story or per-media asset basis * New template type, utility template, not associated with any individual element or category. Useful for creating libraries of utility templates. * Ability to clone stories. * Improved Burner methods, including a status method (to determine if a template is being executed by a preview or a publish event) and methods to assist in the creation of links to other pages within a story. * Improved browser support and performance, thanks to converting the style sheet and JavaScript components to static files. This change incidentally correct issues with IE on the Mac and Netscape 4.x on Windows. * Assets may now optionally be transfered from one workflow to another. * Numerous performance enhancements. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=132744. Although this release gives every appearance of being as stable as any previous release of Bricolage, it does contain a fair bit of new code that needs to be put through the ringer. We also expect other features to be added before the 1.6.0 release, including further performance enhancements, more comprehensive testing, and a localized UI. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. A comprehensive, actively-developed open source CMS, Bricolage has been hailed as Most Impressive in 2002 by eWeek. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
Re: OSCON ideas
On Wednesday, January 8, 2003, at 01:14 PM, Perrin Harkins wrote: 1) Database Objects in Perl 2) The Perl Pet Store What do you guys think? I say both. :-) David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.4.6
The Bricolage team is pleased to announce the release of Bricolage 1.4.6, the Apache/mod_perl enterprise content management system. This maintenance release, which will likely be the final 1.4.x release, fixes over 20 bugs in version 1.4.5 Among the more important bug fixes are the following: * Bric::SAOP::Handler now properly logs fatal errors that are strings rather than exceptions. * Fixed bug in publish code that was attempting to use the Apache request object as a media asset. Thanks to John Greene for the spot. * Category permissions are now properly checked on assets when they're not in workflow as well as when they are in workflow. This means that if a group of users is granted permission to access stories in a category, they can now access those stories even if they're not in workflow. * The search interface for locating media and story assets to relate to a story now checks the permissions of the assets found and only displays the assets for which the user has at least READ permission. Thanks to Sean Greathouse for the spot. * Contributor Association now includes search options and only currently-associated contributors are displayed before searching. * The ability to select different fields by which to sort a list of objects now works again. [David] * Fixed reordering code for subelements. The select list for subelements should now always have an appropriate value. * Date fields can now be unset. That is, if each of the select fields is set to its label, rather than a value, it'll stay that way. This was first noticed with the Expire Date in stories. Thanks to Philip Fibiger for the spot. * Modified installation CREATE DATABASE command to always create the database with the encoding set to UTF-8 (UNICODE). [David] All users of earlier versions of Bricolage are encouraged to upgrade. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=132033. ABOUT BRICOLAGE Bricolage, hailed as Most Impressive in 2002 by eWeek, is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete HTML::Mason support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
Modules Executed Twice
Hi All,
I'm developing a new module for mod_perl 1.27, and I'm noticing that
some code is getting executed twice when the Apache server starts up.
Here's a simple example. Say I have two modules in separate files:
package DoubleTest;
use strict;
my $seen;
sub test_seen {
$seen++;
warn Seen: $seen\n
}
1;
package TestSeen;
use strict;
use DoubleTest;
DoubleTest::test_seen();
1;
Then I have an httpd.conf with these two lines:
PerlModule DoubleTest
PerlModule TestSeen
When I start up Apache, I see Seen: 1 print to the terminal, and then
I see Seen: 2 in the error log. For some reason, TestSeen is getting
executed twice!
I did a quick search on perl.apache.org, and found this item:
http://perl.apache.org/docs/1.0/guide/
config.html#Apache_Restarts_Twice_On_Start
However, this seems to indicate that, first, modules will be executed
twice on restart but not on start, and second, that it doesn't affect
PerlModule directives. What I'm seeing above doesn't seem to bear this
out.
Thanks to that item in the guide, I did figure out how to circumvent
the problem by checking $Apache::Server::Starting in
DoubleTest::test_seen():
sub test_seen {
return if $Apache::Server::Starting;
$seen++;
warn Seen: $seen\n
}
So I'm fine with this workaround, but not sure why it's necessary. I
could also change TestSeen.pm to only call test_seen() in a BEGIN block
or something (since the modules seems to be compiled only once, but run
twice), but since the module I'm actually writing is the equivalent of
DoubleTest with TestSeen as the client, I'd rather not impose that on
the users of my module.
Explanations and other suggested approaches to handling this problem
will be most welcome.
TIA,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Re: Modules Executed Twice
On Monday, December 30, 2002, at 02:45 PM, Stas Bekman wrote:
David Wheeler wrote:
Hi All,
I'm developing a new module for mod_perl 1.27, and I'm noticing that
some code is getting executed twice when the Apache server starts up.
It was supposed to be fixed in 1.25_01:
=item 1.25_01 - July 6, 2001
...
fix double-loading bug of Perl{Require,Module}s at startup time
Hrm, interesting. I wonder what the problem is?
Indeed, that's the workaround that was added originaly to cure the
above problem. Perhaps you can play with httpd_conf and see why it
doesn't work for you. I know that several people have reported that
they still had this problem since 1.26 was released.
I have a better workaround, now. I found that I could make the problem
go away by reversing the order in which the modules are loaded in
httpd.conf:
PerlModule TestSeen
PerlModule DoubleTest
Not exactly sure why that makes a difference, though.
Is httpd_conf() documented somewhere? I can't see what's supposed to be
passed to it.
Thanks,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Re: Modules Executed Twice
On Monday, December 30, 2002, at 04:09 PM, Perrin Harkins wrote: My suggestion in the past has been to PerlRequire a startup.pl that does a use on your modules, instead of pulling them in with PerlModule. Of course, if you turn PerlFreshRestart on then this is the intended behavior. That's exactly what I do, too. But I want to give users the flexibility to do both. Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Perl Cookbook modperl chapter
On Wednesday, December 11, 2002, at 03:17 PM, Ron Savage wrote: Having 2 books which can both be casually, if incorrectly, called The mod_perl Cookbook, is asking for endless (minor) trouble. A distinct name would be a distinct advantage. Nat's book is _The Perl Cookbook_, not _The mod_perl Cookbook_, and is the *original* cookbook. He wrote the book on cookbooks, you could say. :-) David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Online Tonight (Bricolage)
On Friday, December 6, 2002, at 09:18 PM, Les Mikesell wrote: I got the workspace side running with only a little fiddling to back out a CPAN-installed Mason 1.15, but still don't understand how to publish pages to a viewing site. Is a working example included or available? I was hoping for something like http://www.plone.org has as a starting point (but of course I want to use apache/mod_perl instead of zope/python). Or do I just have to learn a lot more about Mason myself? Unfortunately, there is no demo site. If you create stories with the default elements in the system and preview them, the default templates will render your stories (in a very ugly way). If you create a Destination to distribute those stories, you can then publish them. But if you want to customize the look and feel of the templates for your own site, you are going to have to learn how to create templates. This is even more true if you create your own elements. The documentation for Mason templates is in Bric::Templates and Bric::AdvTemplates. But no, you don't have to learn Mason; you can use HTML::Template templates, instead, if you like. The documentation for HTML::Template templates is in, you guessed it, Bric::HTMLTemplate. BTW, all of the Bricolage documentation is available online, too, although be aware that the online copies are for the development version of Bricolage. http://bricolage.cc/documentation.html Good luck! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: [mp2] Documentation/LogHandler question
On Wednesday, December 4, 2002, at 06:14 PM, Stas Bekman wrote: Think of 2.0 as 1.0 on mushrooms. I need to give some thought as to how I can include quote gems like this in my sig. For now, though, I'll leave it to Schwern. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Online Tonight
On Thursday, December 5, 2002, at 05:48 PM, Stas Bekman wrote: When you get the mp3, please send us a link, so we can link to it from perl.apache.org! Thanks. Will do. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Online Tonight
All, I will be the featured guest for an hour on the nationally syndicated talk radio show Online Tonight this evening at 8 pm PST (11 pm EST). Host David Lawrence and I be discussing Bricolage, its history, and content management in general. This is my first time on the radio, so it should be interesting. The show is a light, humor-oriented tech talk show, and is, along with Online Today, the most listened to high-tech-oriented talk show on the air today, according to CNET Radio. The show's web site: http://www.online-tonight.com/ To listen in via streaming media: http://www.cnet.com/broadband/0-7227152.html For those who aren't familiar with Bricolage, it's the mod_perl-powered enterprise-class content management software I've been working on for a few years, first at Salon, then for About.com, and now as open-source (free) software on the Internet. The Bricolage web site: http://bricolage.cc/ A Tech analysis in the October 28th eWeek: http://www.eweek.com/article2/0,3959,652977,00.asp Feel free to tune in or even call in and show your support for mod_perl applications. Host David Lawrence and I will also be available via IM during the broadcast. Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: MySQL prepared sql statements?
On Sunday, November 24, 2002, at 01:08 PM, Bas A.Schulte wrote: I'm wondering if I would gain (some) performance by preparing my sql statements once during ChildInit when using MySQL? Does it cache execution plans for sql statements? I know it makes a big difference on Oracle but I'm not sure what MySQL is like in this respect. MySQL doesn't have a prepared statement feature, so you wouldn't get the same kind of performance gain that you would with Oracle. That said, DBD::mysql does a bit of munging with your statements, and if you use prepare(), it does that munging only once per statement. The upshot: Use prepare() whenever possible to maximize performance. Even better, used prepare_cached() for statements you'll be using a lot, and then they'll be prepared only the first time prepare() is called (per Apache child). Doing so will also make it easier to gain the performance benefit if you later decide to switch to a database such as Oracle that supports prepared statements in the database. Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.4.5
The Bricolage team is pleased to announce the release of Bricolage 1.4.5. This maintenance release fixes over 25 bugs in version 1.4.4 and, as a bonus, makes a few significant changes that affect how it works, to whit: * Categories are now displayed by their URIs instead of their names wherever possible. * Improved error handling by the SOAP server. Full errors will now be printed to the Apache error log, error messages sent back to the client are properly escaped, and all database transactions for a single request will be rolled back in the event of an error. Among the more important bug fixes are the following: * The Bricolage SOAP interface will no longer allow the creation of stories and media with duplicate URIs. * The burner no longer fails when it publishes an asset that's not on a desk. * SOAP now does the proper thing when deleting assets, removing them from desks and workflow only if they're on desks and in workflow. * Setting permissions on the assets in a category works again. * Stories, media, and templates created but not saved no longer disappear into the void. They are instead moved into workflow, put on a desk, and saved as soon as they were created. * The SOAP interface now properly logs events for its activities. All users of earlier versions of Bricolage are encouraged to upgrade. For a complete list of the changes, see the changes file at https://sourceforge.net/project/shownotes.php?release_id=122230. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
Re: Bricolage in eWeek
On Wednesday, October 30, 2002, at 12:53 PM, Aaron Johnson wrote: This weeks print version of eWeek as well as the online version have an article on Bricolage. article - http://www.eweek.com/article2/0,3959,652977,00.asp Bricolage - http://bricolage.thepritgroup.com Holy shit! This is the first I've heard of it! Nice article! I just have to write them to thank them and tell them the new URL... David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.4.4
The Bricolage team is pleased to announce the release of Bricolage 1.4.4. This is a maintenance release that fixes numerous bugs found in version 1.4.3. All users of earlier versions of Bricolage are encouraged to upgrade. The most significant change in this release is that the default character set has been changed from ISO-8859-1 to UTF-8. With this setting, Bricolage does no character set translation, so it's faster. Furthermore, since most users are likely not doing chracter translation in their templates, and the Bricolage API outputs UTF-8, it seemed better to use the same character set from end-to-end by default. Other changes include a few interface improvements, unlimited data sizes in elemente fields, more exact error messages and prompts, and over 20 bug fixes. ABOUT BRICOLAGE Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. For a complete list of the changes, see the changes file at http://sourceforge.net/project/shownotes.php?release_id=118945. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
ANNOUNCE: Bricolage 1.4.2
The Bricolage team would like to announce the release of Bricolage 1.4.2. This is a maintenance release that fixes several critical bugs in version 1.4.1. All users of earlier versions of Bricolage are strongly encouraged to upgrade. Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. For a complete list of the changes, See Bric::Changes at http://bricolage.cc/docs/Bric/Changes.html. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
ANNOUNCE: Bricolage 1.4.1
The Bricolage team would like to announce the release of Bricolage 1.4.1. This is a maintenance release with many bug fixes. All users of earlier versions of Bricolage are strongly encouraged to upgrade. Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features (see below). It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. For a complete list of the changes, See Bric::Changes at http://bricolage.cc/docs/Bric/Changes.html. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Enjoy! --The Bricolage Team
ANNOUNCE: Bricolage 1.4.0
The Bricolage team would like to announce the release of Bricolage 1.4.0. This is the first new stable release of Bricolage since the release of version 1.2.3 in March, and the first major release since 1.2.0 in January. Bricolage is a full-featured, enterprise-class content management and publishing system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features (see below). It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. For a complete list of the changes, See Bric::Changes at http://bricolage.cc/docs/Bric/Changes.html. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. Here's a sampling of the major new features in version 1.4.0: * An integrated SOAP (Simple Object Access Protocol) server, which offers a convenient interface for importing and exporting content, as well as for mass-publishing content. * Simplified installation via an included Makefile and related scripts that check for dependencies, build the database, and install all the required libraries, components, and programs. * Content distribution via FTP and SFTP, in addition to the existing file system copy methods. * System-wide customization of the URIs the Bricolage builds for content. * Improved tracking of the publish status of content, easing the identification of what needs to be published and what doesn't. * Search result paging. A new system-wide preference allows those manager screens that display a lot of objects to paginate those results over a series of pages. * Improved performance of the keyword system, the category system, the group system, the publishing system, and caching. * A new interface for managing media types (a.k.a., MIME types) so that Bricolage can better identify the types of media files it manages. * Support for Apache-SSL in addition to the existing support for mod_ssl. * Simplified configuration system, with support for manual configuration where desired. * System cloning. Bricolage installations can now be cloned, complete with all data stored in the RDBMS, and converted into a distribution tarball. This simplifies the creation of packages for installing customized copies of Bricolage. * The ability to use Bricolage with or without SSL support on arbitrary ports. * Support for Mac OS X. * Over 90 bug fixes. Enjoy! --The Bricolage Team -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Change in module naming conventions
On Tuesday, August 27, 2002, at 09:29 AM, Per Einar Ellefsen wrote: - I created the Apache::Util:: namespace. However, one person thought the Persistent:: namespace to be too specific, and would prefer to rename Apache::Util:: to something like ::Misc, ::Lib, ::Extensions or ::Addons, and add the Persistent:: modules there. What do you think? I like Apache::Util, and don't have a problem with Apache::Util::Persistent. Makes sense to me. - I originally had Apache::Auth::Authen, ::Authz and ::Access, but Robin Berjon told me he preferred to have the 4 as top-level namespaces. What do people think? I agree with Robin. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Change in module naming conventions
On Tuesday, August 27, 2002, at 09:46 AM, Per Einar Ellefsen wrote: It's actually Apache::Persistent, because the persistence modules in it have big differences from the Apache::Util modules. Oh. So what's the complaint about Apache::Util:: ? David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.3.3
The Bricolage developers are pleased to announce the release of Bricolage version 1.3.3! This the release candidate for Bricolage verion 1.4.0, and is considered feature-complete. Nearly 50 new features have been added since the 1.2.2 release, and over 80 bugs fixed. Barring any unforseen major bugs cropping up, 1.4.0 will be released within a week of this release. Please feel give it a try, and report any issues to the Bricolage Bugzilla database, at http://bugzilla.bricolage.cc/. Learn more about Bricolage and download it from the Bricolage home page, http://bricolage.cc/. General description: Bricolage is a full-featured, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Enjoy! --The Bricolage Team
Re: Simple Database connect
On Friday, August 16, 2002, at 07:52 AM, Pierre Vaudrey wrote: dyld: /usr/sbin/httpd multiple definitions of symbol __dig_vec /usr/libexec/httpd/libphp4.so definition of __dig_vec /Library/Perl/darwin/auto/DBD/mysql/mysql.bundle definition of __dig_vec dyld: /usr/sbin/httpd multiple definitions of symbol __dig_vec /usr/libexec/httpd/libphp4.so definition of __dig_vec /Library/Perl/darwin/auto/DBD/mysql/mysql.bundle definition of __dig_vec It looks as though you have some symbol conflicts between PHP and MySQL. Try turning off libphp.so. If that works, you may need to recompile PHP and/or MySQL. HTH, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Mason 1.12
On Saturday, August 3, 2002, at 03:44 AM, Lupe Christoph wrote: Larry was anticipating a long line of Perl 5 versions... (Yes, I know $] is deprecated. But $^V does not print easily. And vector version numbers are not compatible with 5.005 and earlier, so CPAN modules avoid them.) Not only that, but Cmake dist couldn't pick up v-numbers -- at least not in 5.6.x. Not sure about 5.8.0. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Mason 1.12
On Thursday, August 1, 2002, at 01:43 PM, Dave Rolsky wrote: It can, but I'm not sure what to update it to. Frankly, I think CPAN is more at fault here given that _many_ people use CVS for this sort of stuff and this quite normal when using CVS. No, CVS is kind-of brain-dead about this. I suggest you use sprintf to properly format the version number with appropriate number of 0s. Although, with those version numbers, it might be a little late. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
[OT] Re: ANNOUNCE: Mason 1.12
On Thursday, August 1, 2002, at 02:11 PM, Dave Rolsky wrote: See, that's the problem. We're up in the hundreds. Maybe we should've started formatting these with '%04d' way back when but that certainly wouldn't help now. I've given up on letting CVS set $VERSION, for just this reason. It's a major PITA. I set $VERSION manually. Or we could just use the CVS revision as an integer, not a float. That is weirder in some ways, but will just work right forever. Hm, not sure I understand how this would work. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Apache-print Timed Out
On 7/21/02 8:19 AM, Ask Bjoern Hansen [EMAIL PROTECTED] claimed: You didn't tell which version of MSIE they use; but if it's not recent it could be some CSS that makes the browser act up[1]. V.5, I think. It doesn't happen on OS X, though, only OS 9. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Apache-print Timed Out
I think I made a mistake posting this query over the holiday weekend, so I'm gonna speak up again. I have a couple of strange bugs showing up in Bricolage that have something to do with Apache-print timing out (with Win 95 and Mac OS 9 -- yes, these folks need to join the new millennium), and have no idea how or under what circumstances print times out. Any enlightenment on this issue would be most welcome. Thanks! David On 7/5/02 1:25 PM, David Wheeler [EMAIL PROTECTED] claimed: Hi All, I'm seeing some strange behavior with IE/Mac OS Classic where pages aren't getting completely loaded and I'm seeing this message in the log error log: [Fri Jul 5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl: Apache-print timed out Config: Apache/1.3.26 (Unix) mod_perl/1.27 mod_ssl/2.8.9 OpenSSL/0.9.6b This is on RedHat Linux 7.2. I did a quick google search, but found no obvious answers to this issue. Anyone got any ideas what could be happening? Why and under what circumstances will Apache-print time out? TIA, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Apache-print Timed Out
Hi All, I'm seeing some strange behavior with IE/Mac OS Classic where pages aren't getting completely loaded and I'm seeing this message in the log error log: [Fri Jul 5 20:22:17 2002] [info] [client 192.168.1.1] mod_perl: Apache-print timed out Config: Apache/1.3.26 (Unix) mod_perl/1.27 mod_ssl/2.8.9 OpenSSL/0.9.6b This is on RedHat Linux 7.2. I did a quick google search, but found no obvious answers to this issue. Anyone got any ideas what could be happening? Why and under what circumstances will Apache-print time out? TIA, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Porting to OS X
On 6/4/02 10:43 AM, Noam Solomon [EMAIL PROTECTED] claimed: Can anyone give me a rough idea how much time it would take to move a server serving mod_perl websites from UNIX to OS X? It uses Apache::Session, DBI::Mysql, HTML::Mason, CGI, and Apache::OpenIndex, among others, and uses both AuthHandlers and AuthzHandlers. It depends on how good a Sysadmin you are, but I would say a couple of days. I document how to install most of this stuff on my site: http://david.wheeler.net/osx.html I don't cover MySQL, but there's a link to an Apple article on how to install it in the section where I cover installing PostgreSQL. HTH, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Porting to OS X
On 6/4/02 10:54 AM, Vuillemot, Ward W [EMAIL PROTECTED] claimed: I think it is relatively an easy move, IMHO. Just beaware that the Mac OS filesystem is NOT case-sensitive. Which can cause problems with certain applications. . .and we hope (Apple, you listening?) that they will fix this gross over-sight. I don't think that Apple is likely to change this. However, you can install OS X on a case-sensitive partition (UFS?) if you really want to. Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: PDF generation
On 4/19/02 10:33 PM, Stas Bekman [EMAIL PROTECTED] claimed: If your end goal is PS, better generated PS in first place. From my experience ps - pdf - ps, makes the final PS a much bigger file (5-10 times bigger). I use html2ps for generating PS files (used for generating the mod_perl guide's pdf). Actually, I realized the same thing yesterday. I'm looking at possibly just using PostScript::Document to create PS and forgetting about PDF for now. Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: PDF generation
On Wed, 03 Apr 2002 16:01:24, Drew Taylor [EMAIL PROTECTED] wrote: I can highly recommend PDFLib. It's not quite free in that you have to buy a license if you make a product out of it, but it's still cheap. Matt Sergeant has recently added an OO interface over the PDFLib functions with PDFLib. http://search.cpan.org/search?dist=PDFLib This looks pretty good to me. Can anyone suggest how I might programmtically send a PDF to a printer once I've generated it in Perl/mod_perl? Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: [JOB] ModPerl developer at PrintMe.Com
John, I saw your post for a ModPerl Developer on the mod_perl list and would like to apply. Please find enclosed my resume. As a quick overview, please note my experience leading a team of engineers and specialists in remotely developing and delivering an Apache/ModPerl/HTML::Mason/PostgreSQL-based enterprise content management application for Salon.com and later Primedia. In my planning and implementation of this software, I strove to provide an effective yet intuitive application to meet the content management needs of large organizations. I also managed the project development schedule, recruiting talent, and managing the development infrastructure and process from end to end. The payoff for this work is reflected in the success of the software: It is now a critical part of the enterprise asset management infrastructure of Primedia; Salon.com; and the World Health Organization in Geneva, Switzerland. I'd like to put my skills developing successful enterprise-class applications to work for PrintMe.com. I thrive in an environment where I work hard to architect, design and develop successful products that exceed expectations. Please feel free to contact me any time. I live in San Francisco, so it will be easy for me to commute to Foster City. I look forward to hearing from you. Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED] resume.txt Description: Binary data
Re: [JOB] ModPerl developer at PrintMe.Com
On 4/13/02 1:54 PM, David Wheeler [EMAIL PROTECTED] claimed: John, I saw your post for a ModPerl Developer on the mod_perl list and would like to apply. Please find enclosed my resume. Did I *really* I reply to the whole list??? Oh, god, am I embarrassed. Sorry for the spam, everyone! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Hello again
On 4/9/02 8:24 AM, John Kolvereid [EMAIL PROTECTED] claimed: These are GREAT URLs for installing mod_perl. I wish I would have known about them sooner. Whatever. After reading the DSO section I'm not sure I have configured mod_perl as DSO. In fact, I'm not sure what I DO have. httpd -l will tell you what you have. HTH, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.2.3
The Bricolage development team is proud to announce the release of Bricolage version 1.2.3. This is a maintenance release with many bug fixes. It replaces the 1.2.2 release, which , due to a packaging error, was a broken distribution. All Bricolage 1.1.x and 1.2.x users are strongly encouraged to upgrade to this version in order to take advantage of its greater stability and reliability. Here's a brief description of Bricolage: Bricolage is a full-featured, open-source, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. More information on Bricolage can be found on its home page. http://bricolage.thepirtgroup.com/ And it can be downloaded from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=34789 --The Bricolage Team -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.2.2
The Bricolage development team is proud to announce the release of Bricolage version 1.2.2. This is a maintenance release with many bug fixes. All Bricolage 1.1 and 1.2 users are strongly encouraged to upgrade to this version in order to take advantage of its greater stability and reliability. Here's a brief description of Bricolage: Bricolage is a full-featured, open-source, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. More information on Bricolage can be found on its home page. http://bricolage.thepirtgroup.com/ And it can be downloaded from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=34789 --The Bricolage Team -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: File upload example
On Tue, 2002-03-12 at 03:57, Rich Bowen wrote:
my $form = Your::Class::form(); # Wherever you put this function
if (my $file = $form-{UPLOAD}) {
my $filename = $file-filename; # If you need the name
Actually, if you want the name, it's a really good idea to just get the
basename, since some browsers on some platforms (e.g., IE/Mac) send the
complete path name to the file on the browser's local file system (e.g.,
':Mac:Foo:Bar:image.jpg'). This is trickier than it sounds, because you
have to tell basename() what platform to assume the file is from. Here's
how I suggest doing it.
use File::Basename;
use HTTP::BrowserDetect;
my $browser = HTTP::BrowserDetect-new($ENV{HTTP_USER_AGENT});
# Tell File::Basename what platform to expect.
fileparse_set_fstype($browser-mac ? 'MacOS' :
$browser-windows ? 'MSWin32' :
$browser-dos ? 'MSDOS' :
$browser-vms ? 'VMS'
$browser-amiga ? 'AmigaOS' :
$^O);
# Get the file name.
my $filename = basename($file-filename);
# Be sure to set File::Basename to the local file system again.
fileparse_set_fstype($^O);
HTH,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Re: mod_perl training companies?
On Thu, 2002-03-07 at 01:17, Stas Bekman wrote: *** there is this modperl development company in Belgrade, they are very good. --- Which company you are talking about *** the modperl development company of course! --- but what company are you talking about? ... two hours later ... --- sorry, I still don't know what company you are talking about. *** the modperl company!!! Aarrrgg Hope you get the idea ;) Don't you watch That 70s show? David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE Bricolage-Devel 1.2.1
Announcing the release of Bricolage 1.2.1. This version is primarily a maintenance release with many bug fixes. It does offer one major new feature, however. Configuring Bricolage in your Apache server has become much simpler with the introduction of the new Bric::App::ApacheConfig module. Using this module, configuring Apache can now be done in two lines: PerlPassEnv BRICOLAGE_ROOT PerlModule Bric::App::ApacheConfig See INSTALL for information on how to configure Bricolage itself, and on how to run Bricolage as a virtual host on your server. Here's a brief description of Bricolage: Bricolage is a full-featured, open-source, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. More information on Bricolage can be found on its home page. http://bricolage.thepirtgroup.com/ And it can be downloaded from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=34789 Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.(sm) -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE Bricolage-Devel 1.2.1
Doh! Sorry, that's just Bricolage 1.2.1, not Bricolage-Devel. That's what I get for not looking things over carefully enough! Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: [ANNOUNCE] libapreq 1.0 released
On Fri, 2002-02-22 at 12:43, Jim Winstead wrote: (this is the package that provides Apache::Request and Apache::Cookie.) snip / Okay, just so I'm clear, does this version of libapreq compile on Mac OS X just like on any other *nix? You don't mention support for Mac OS X in the Changes... Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE Bricolage-Devel 1.3.0
Announcing the release of Bricolage 1.3.0. This is a development release for the forthcoming 1.4.0 release. It features many bug fixes planned for the forthcoming 1.2.1 release, as well as a new feature: A SOAP server. The SOAP server will enable automatic publishing of content, as well as importing and exporting assets. Here's a brief description of Bricolage: Bricolage is a full-featured, opne-source, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming \ language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. More information on Bricolage can be found on its home page. http://bricolage.thepirtgroup.com/ And it can be downloaded from SourceForge. http://sourceforge.net/project/showfiles.php?group_id=34789 Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.(sm)
Re: ANNOUNCE Bricolage-Devel 1.3.0
On Thu, 2002-02-21 at 20:38, Stas Bekman wrote: I've added the description at http://perl.apache.org/#appservers Thanks David! Cool -- thanks Stas. Although I might want to send a slightly longer description for inclusion there soon... Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Perl Section Bug?
On Wed, 2002-02-13 at 20:44, Salvador Ortiz Garcia wrote: Ok, I found it. Right now all Location, Directory and Files are afected by being upgraded at random to the Match versions. Ugly. Can you please test the following patch for perl_config.c: snip / Yes, that does indeed correct the problem. Thank you. Right now I'm working in a more radical patch to fix other minor problems related to Perl sections handling. Can I assume that the fixes will be in 1.27? Does Doug have plans for another release soon? Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: Perl Section Bug?
On Fri, 2002-02-08 at 20:25, Salvador Ortiz Garcia wrote: Yes, It's a bug in Perl Sections. Confirmed in 1.26. snip / I'm digging into it. Thanks. I'm glad to know that I'm not imagining things. We've just found a place in Bricolage where the Location directive *does* work as expected. So you're right -- it's worse. Ugh. Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: choice of mod_perl technology for news site
On Thu, 2002-02-07 at 17:30, Ian Kallen wrote: I'm not really involved with the project but it looks to me that bricolage is heading towards content generation abstraction (there's support for Mason and HTML::Template). Therefore, I would imagine that if you wanted to use AxKit as a content generator, you could. Yes, this is true. Bricolage features a pluggable Templating architecture, which means that any templating system could be added. Currently it supports HTML::Mason and HTML::Template. Those who'd like to contribute Template Toolkit and XML/XSLT/AxKit support would be welcomed! Join the Bricolage developers list and join the discussion there if you're interested. https://sourceforge.net/mail/?group_id=34789 Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Perl Section Bug?
Okay, let me try again.
I have a simple module I've written that demonstrates the problem. here
it is:
package MyTest;
our $VERSION = '0.1';
use Apache;
sub one {
print STDERR One\n;
print STDOUT One\n;
return Apache::OK;
}
sub two {
print STDERR Two\n;
print STDOUT Two\n;
return Apache::OK;
}
package Apache::ReadConfig;
use strict;
use warnings;
our $NameVirtualHost = '*:80';
our %VirtualHost = ('*:80' = {
ServerName = '_default_',
DocumentRoot = '/usr/local/apache/htdocs',
Location = {
'/one' = {
SetHandler = 'perl-script',
PerlHandler= 'MyTest::one'
},
'/two' = {
SetHandler = 'perl-script',
PerlHandler= 'MyTest::two'
}
}
});
Now, if I execute this from httpd.conf by simply calling
PerlModule MyTest
Here's what I get for my requests:
URL Prints
=== ==
http://myserver/one One
http://myserver/two Two
http://myserver/one/foo One
http://myserver/two/foo Two
http://myserver/one/two One
http://myserver/one/twofoo One
http://myserver/one/two/foo One
http://myserver/two/one One
http://myserver/two/onefoo One
http://myserver/two/one/foo One
It's the last three requests that are the problem. Because I'm hitting
the '/two' location, I expect each of those examples to print Two. But
because they each have one in the URL, they all print One!
Why is this? It seems to be acting like LocationMatch directives rather
than Location. Could this be a bug in how the Perl sections work? If
not, how do I get that last request to print Two instead of One?
Even if it *is* a bug, how do I get the proper behavior?
TIA,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Re: Perl Section Bug?
On Fri, 2002-02-01 at 18:56, David Wheeler wrote: snip / Why is this? It seems to be acting like LocationMatch directives rather than Location. Could this be a bug in how the Perl sections work? If not, how do I get that last request to print Two instead of One? Even if it *is* a bug, how do I get the proper behavior? Okay, in a way, I've answered my own question. Prepending ^ to the front of each Location directive corrects the problem. However, I still think that this is a bug, because AFAIK, Location directives aren't supposed to use regular expressions unless they have the '~' character in them. I'm not sure how one would include that in Perl sections, but it seems better to require that Perl sections interpret Location directives as literal strings and LocationMatch directives as regular expressions Make sense? Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED] Kineticode. Setting knowledge in motion.(sm)
Location Directives Problem
Hi All,
Below I have the output of Apache::PerlSections-dump from Bricolage.
I'm doing a lot of configuration in a Perl module where I simply switch
to the Apache::ReadConfig package and do my thing. This keeps httpd.conf
clean but allows me to do all the data munging I need to to get all the
proper locations set up according to the settings of Bricolage's own
configuration directives.
The problem is that the Location directives below are acting more like
LocationMatch directives. For example, if I hit the URL
'/admin/workflow/media', I would expect the '/' Location's handlers to
handle the request. But they're not. Instead, it's the '/media' Location
handlers. It's as if I had set it up with LocationMatch */media* instead
of Location.
Anyone have any idea why it might be doing this? I've tried all kinds of
things and I'm stumped!
TIA,
David
#hashes:
%VirtualHost = (
'*:80' = {
'Location' = {
'/' = {
'PerlHandler' = 'Bric::App::Handler',
'PerlCleanupHandler' = 'Bric::App::CleanupHandler',
'PerlAccessHandler' = 'Bric::App::AccessHandler',
'SetHandler' = 'perl-script'
},
'/login' = {
'PerlHandler' = 'Bric::App::Handler',
'PerlCleanupHandler' = 'Bric::App::CleanupHandler',
'PerlAccessHandler' = 'Bric::App::AccessHandler::okay',
'SetHandler' = 'perl-script'
},
'/logout' = {
'PerlCleanupHandler' = 'Bric::App::CleanupHandler',
'PerlAccessHandler' = 'Bric::App::AccessHandler::logout_handler'
},
'/data' = {
'SetHandler' = 'default-handler'
},
'/data/preview' = {
'PerlFixupHandler' = 'sub { $_[0]-no_cache(1); return Apache::OK; }'
},
'/dist' = {
'PerlHandler' = 'Bric::Dist::Handler',
'SetHandler' = 'perl-script'
},
'/media' = {
'PerlCleanupHandler' = 'Apache::OK',
'PerlAccessHandler' = 'Apache::OK',
'SetHandler' = 'default-handler'
}
},
'DocumentRoot' = '/usr/local/bricolage/comp',
'DefaultType' = 'text/html',
'ServerName' = '_default_',
'PerlTransHandler' = 'Bric::App::PreviewHandler::uri_handler'
}
);
#arrays:
@NameVirtualHost = (
[
'*:80'
]
);
#scalars:
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
UI Regression Testing
Hi All, A big debate is raging on the Bricolage development list WRT CVS configuration and application testing. http://www.geocrawler.com/mail/thread.php3?subject=%5BBricolage-Devel%5D+More+on+Releaseslist=15308 It leads me to a question about testing. Bricolage is a monster application, and its UI is built entirely in HTML::Mason running on Apache. Now, while we can and will do a lot more to improve the testing of our Perl modules, we can't really figure out a way to automate the testing of the UI. I'm aware of the the performance testing utilities mentioned in the mod_perl guide -- http://perl.apache.org/guide/performance.html -- but they don't seem to be suited to testing applications. Is anyone familiar with how to go about setting up a test suite for a web UI -- without spending an arm and a leg? (Remember, Bricolage is an OSS effort!). Thanks! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: UI Regression Testing
On Fri, 2002-01-25 at 10:12, Perrin Harkins wrote: Have you tried webchat? You can find webchatpp on CPAN. Looks interesting, although the documentation is rather sparse. Anyone know of more examples than come with it? Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: performance coding project? (was: Re: When to cache)
On Fri, 2002-01-25 at 09:08, Perrin Harkins wrote: snip / It's much better to build your system, profile it, and fix the bottlenecks. The most effective changes are almost never simple coding changes like the one you showed, but rather large things like using qmail-inject instead of SMTP, caching a slow database query or method call, or changing your architecture to reduce the number of network accesses or inter-process communications. qmail-inject? I've just been using sendmail or, preferentially, Net::SMTP. Isn't using a system call more expensive? If not, how does qmail-inject work? Thanks, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: performance coding project? (was: Re: When to cache)
On Fri, 2002-01-25 at 13:15, Matt Sergeant wrote: With qmail, SMTP generally uses inetd, which is slow, or daemontools, which is faster, but still slow, and more importantly, it anyway goes: perl - SMTP - inetd - qmail-smtpd - qmail-inject. So with going direct to qmail-inject, your email skips out a boat load of processing and goes direct into the queue. Okay, that makes sense. In my activitymail CVS script I just used sendmail. http://www.cpan.org/authors/id/D/DW/DWHEELER/activitymail-0.987 But it looks like this might be more efficient, if qmail happens to be installed (not sure on SourceForge's servers). Of course none of this is relevant if you're not using qmail ;-) Yes, and in Bricolage, I used Net::SMTP to keep it as platform-independent as possible. It should work on Windows, even! Besides, all mail gets sent during the Apache cleanup phase, so there should be no noticeable delay for users. David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Bricolage 1.2.0
On Fri, 2002-01-11 at 01:29, [EMAIL PROTECTED] wrote: Do you provide a demo of Bricolage. Can I expect something similar to the Midgard Project on PHP? Unfortunately there is no demo of Bricolage at this time. But you can start reading up on it and see some screenshots at http://bricolage.thepirtgroup.com/. I'm not familiar with Midgard, though it looks interesting. What differentiates Bricolage from other OSS CMSs, however, is its robust support for configurable workflows. Furthermore, its templates are written in HTML::Mason or HTML::Template -- that is, Perl. So you have a complete, robust programming language to work with. Thanks, David -- David Wheeler AIM: dwTheory Bricolage Maintainer ICQ: 15726394 [EMAIL PROTECTED] Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
Re: ANNOUNCE: Bricolage 1.2.0
On Fri, 2002-01-11 at 11:39, Matt Sergeant wrote: Looks neat! Thanks, Matt! Any chance of supporting more template systems in the future, like TT and XSLT? The templating architecture is managed via subclasses. So anyone who wants to add his/her favorite templating system is welcome to implement a new subclass. I encourage interested developers to join the bricolage-devel list on SourceForge. https://sourceforge.net/mail/?group_id=34789 Regards, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
ANNOUNCE: Bricolage 1.2.0
I'd like to announce the release of Bricolage 1.2.0. It will shortly be available for download from http://bricolage.sourceforge.net/. This release features several bug fixes and quite a few important new features. It uses HTML::Mason exlusively for its UI, and uses either HTML::Mason or HTML::Template for its templating architecture. Here's a brief description of Bricolage: Bricolage is a full-featured, enterprise-class content management system. It offers a browser-based interface for ease-of use, a full-fledged templating system with complete programming language support for flexibility, and many other features. It operates in an Apache/mod_perl environment, and uses the PostgreSQL RDBMS for its repository. Here's a list of the changes from 1.0.2: VERSION 1.2.0 New Features * Added Context-sensitive, online help. [Sam] * Added separate interface for editing templates (via FTP). [Sam] * Added the ability to use HTML::Template Templates. [Sam] * Added ability for differnt Output Channels to function as different component roots for in Mason templates. This will allow for templates that can't be found in the current Output Channel to be searched for in other Output Channels. [David] * Added link to Event log to Find Story, Find Template, and Find Media screens. [David] * Added true previewing for media assets. Now, when you click their URIs to preview them, they will be distributed to the preview server(s) before redirecting the user to them, rather than just serving them up from where they live on the Bricolage file system. The latter can still be accessed under Download in the Media Asset profile. This will continue to be the preferred way to grab media files for editing and such, as it will not incur the overhead of distributing the media file. [David] * Allow only one template with a given name for a given category, element, burner and output channel. [Sam] * Added a Maintainer section to the About page. [David] * Updated About page to mimic the layout of the help pages. [David] Bug Fixes * Fixed a bug with local previews where a preview page could show up instead of the Bricoalge UI. Thanks to Sara for the spot. [David] * Fixed a bug where Mason component calls failed in previews when the PREVIEW_MASON directive was enabled. [David] * Changed default value for text area fields added via the form builder (i.e., in Contributor Type and Element profiles) to 0. The values 0 and always make the the new field unlimited in length. [David] * Fixed a couple of buttons to be proper case rather than upper case. [David] * Separated the filesystem destinations for assets burned for publication and for assets burned for previewing. This will prevent someone previewing and stomping all over a published version of an asset before the published version is distributed. [David] * Removed hard-coding of the local preview directory in httpd.conf and httpd-ssl.conf. Now using the values stored in PREVIEW_LOCAL, instead, to determine the proper directory. [David] * Added the DEF_MEDIA_TYPE directive. Bricolage will use the value in this directive to assign a Media Type to all file resources if they Bricolage can't figure it out from their file extentions. This fixes a bug where Bricolage would choke if it couldn't figure out the MediaType itself. [David] Enjoy! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
DSO Issues
Hi All, While it seems to be well-known anecdotally that one should never use a DSO install of mod_perl (particularly among Mason developers), is there yet any place where all the known issues surrounding the use of DSO mod_perl are documented? I see a place in the guide where Stas mentions issues with mymalloc and such, but I also saw a post from a few months ago where he'd asked for someone with extensive experience with DSO installs to come forward and discuss the known issues. Did this ever come about? Thanks! David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
RE: no_cache()
On Fri, 2001-11-16 at 11:59, Kyle Oppenheim wrote:
$r-no_cache(1) adds the headers Pragma: no-cache and Cache-control:
no-cache.
snip /
Huh, according to the mod_perl guide:
http://thingy.kcilink.com/modperlguide/correct_headers/2_1_3_Expires_and_Cache_Control.html
Those headers are not added by no_cache(1). But I see that, according to
the mod_perl Changes file, those headers were added to the behavior of
no_cache(1) in mod_perl 1.21_01. So perhaps the mod_perl guide should be
changed from its current documentation:
my $headers = $r-headers_out;
$headers-{'Pragma'} = $headers-{'Cache-control'} = 'no-cache';
$r-no_cache(1);
To simply:
$r-no_cache(1).
Stas?
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Re: Log Phase
On Sat, 18 Aug 2001, Perrin Harkins wrote: Is there any way to get the content handling phase to send the content to the client before the logging phase executes? Just use a cleanup handler instead of a log handler. Thank you, Perrrin! That was *exactly* what I needed to know! And it works great! Best, David -- David Wheeler AIM: dwTheory [EMAIL PROTECTED] ICQ: 15726394 Yahoo!: dew7e Jabber: [EMAIL PROTECTED]
