Re: [RFC] two ajax-related packages

2007-02-19 Thread Randy Kobes

On Tue, 6 Feb 2007, Jonathan Vanasco wrote:

I'm going to talk in context of CGI::Apache2::Ajax, as I 
haven't had time to look at the rest.


	Personally, I would like to see something in terms of ENV variables 
that one can set to force it to use libapreq or cgi pm
	Thats just because every now and then I  switch from one to the other 
to debug


I also like to do that switch. However, I think that'd
more naturally be done at the level of the application;
the purpose of this module was just to provide a few
CGI.pm-compatible methods via mod_perl2/libapreq2. The
interface used is such that, within an application, one
can do
my $cgi;
if ($some_condition_is_met) {
   $cgi = CGI::Apache2::Ajax->new($r);
}
else {
   $cgi = CGI->new($r);
}
my $foo = $cgi->param("foo");
and so can switch between CGI.pm and mod_perl2/libapreq2
by adjusting $some_condition_is_met; the method calls
on $cgi are intended to be compatible.


my other comment is the name:
		its just a bit confusing as it doesn't really handle a lot of 
functionality and abstracts other items.  perhaps something like 
CGI::Apache2::AjaxProvider , Apache2::AjaxProvider, or even 
CGI::AjaxProvider.  also , just a thought - but something like that seems 
more inline with the purpose of your module.


That's a good suggestion. A couple of people off-list also
raised this, and one suggestion was CGI-Apache2-Wrapper.
CGI::Ajax wants it to start with "CGI", so this sounds
like a good name. I've adjusted Apache2-Ajax and
Apache2-Autocomplete to use this if available; all three
packages are now making their way around CPAN.

Thanks!

--
best regards,
Randy


ANNOUNCE: Krang v2.100

2007-02-19 Thread Sam Tregar

Krang v2.100 is now available (the source release is up now and binary
builds should be up soon).  Notable changes in this release:

* Numerous bugs were fixed in Krang's most intensive QA cycle in
  years.

* Krang now includes methods to integrate with dynamic front-end
  applications by publishing CGI::Application instance scripts and
  templates.  New methods were added to
  Krang::ElementClass::TopLevel to facilitate this:
  publish_frontend_app_template() and publish_frontend_app_stub().
  [Jesse Erlbaum]

* Modified Site Server configuration to support CGI applications
  and Apache::Registry apps.  This will permit the site server to
  host interactive applications.  [Jesse Erlbaum]

* Added new parameter "mode" to additional_content_block() method
  in the publisher. This new parameter permits the permission of
  the file to be set, which is particularly useful for publishing
  executable files.  [Jesse Erlbaum]

* Added new options to Krang::HTMLPager to allow paging of data
  from external sources.  [Michael Peters]

* Krang now sends no-cache HTTP headers for all Krang::CGI
  requests. This will fix some problems when logging in as a
  different user with the same browser session in IE.
  [Michael Peters]

* Upgraded to HTML::Template v2.9, fixing several bugs. [Sam]

* Added a new configuration variable, PreviewSSL, which controls
  whether links to preview use SSL. This behavior was previously the
  default when EnableSSL was set, but now it is available
  independently and can be turned off even when Krang itself is using
  SSL. [Sam]

* During DB creation, addon SQL files now come after core Krang.
  This allows addons to change existing Krang data/tables.
  [Michael Peters]

* Stricter enforcement of asset permissions. [Michael Peters]

Detailed change-log here: http://krang.sf.net/docs/changelog.html

Krang is an Open Source web-publisher / content-management system
designed for large-scale magazine-style websites.  It is a 100% Perl
application using Apache/mod_perl and MySQL, as well as numerous CPAN
modules.

Krang provides a powerful and easy to use story and media editing
environment for website editors, as well as a complete template
development environment for web designers. On the back-end, Perl
programmers can customize Krang to control the data entered in the
story editor and add code to drive the templates to build output.
Krang can be enhanced with add-ons containing new skins and other new
features.  Krang easily handles large data sets and can manage
multiple websites in a single installation.

For more information about Krang, visit the Krang website:

   http://krang.sourceforge.net/

There you can download Krang, view screenshots, read documentation,
join our mailing-lists and access the CVS tree.

- the Krang team



Sample Web Application that uses mod_perl

2007-02-19 Thread aqua
Dear Group,

Just would like to try mod perl 2.0 in my home system. I have XP, Apache 
2.0.59, mod perl 2.0.3 and perl 5.8.8. I was able to install and run Apache 
with mod_perl successfully.

Could you please let me know if there are any simple sample (complete) 
application available on the net with a HTML form and update the same in a 
(MySQL) database. I am familar with Perl-CGI based web application but I have 
not tried the same with mod_perl (even with PerlRun).

Appreciate your pointers in this regard. 

Best Regards
Dominc

PS: Similar information may be available on this mailing list but I cannot 
search this list.


Apache::PerlVINC

2007-02-19 Thread Mike Seda

Hi All,
I just can't seem to get Apache::PerlVINC working properly. My specs are 
below:


RHEL 4
Apache 1.3.37
mod_ssl 2.8.28
Apache::DBI -- 1.05
Apache::PerlVINC -- 0.03
CGI -- 2.752
DBD::Oracle -- 1.19
DBI -- 1.53
Digest::MD5 -- 2.36
Perl -- 5.6.2
mod_perl -- 1.29

I have two vhosts. One production and one development. There are four 
perl modules that my apps need. There are two versions (prod and dev) 
for each perl module. Of course, I wish the prod vhost to use the prod 
version perl modules.. You get the idea... Is there something special 
that I need to do? I noticed that some people on the web stated that 
"PerlVersionINC On" is required:

http://mail-archives.apache.org/mod_mbox/perl-modperl/27.mbox/[EMAIL 
PROTECTED]
... Yet this is missing from the docs:
http://www.annocpan.org/~DAVEM/Apache-PerlVINC-0.03/PerlVINC.pm
Also, "PerlVersionINC" does not seem to be available since I get a nice 
error stating that PerlVersionINC is missing when trying to start Apache 
while that directive is defined. Any thoughts?

Best,
Mike