Hi Drew,
I have been hinting at an Authentication plugin for a while now, but
haven't finished it yet. I did a little bit more work on it
yesterday, but I don't have any docs, or any tests written for the
module yet.
I you also have a start on a module, maybe we can colaborate. From
your
On Thu, 28 Oct 2004 20:14:58 -0400, Clayton Scott wrote:
Hi Clayton
Can you not adjust the font size in your web browser? The default
My apologies.
I had thought about that, but I did not actually check the current setting. I should
have - it was on 'Smallest'.
--
Cheers
Ron Savage, [EMAIL
Drew and Cees,
I am in the process of converting over a non CGA application to run under
CGA. (Sort of) does the same stuff as CGA in a non-OO way. My application
has implemented user and group authentication and this is what I try to
accomplish from a design perspective.
Run mode level
I was searching through the list archives and I cannot find a mention
(besides this guy[1] asking and not getting a response (to the plugin
question)) of why we should change our code from C:A:ValidateRM to
C:A:P:ValidateRM. I've heard lazy loading thrown around, but I'm not
sure what that
Once these features are moved into CGI::App, I see the documentation
appearing a little out of the way in a section on WRITING PLUGINS or
Advanced Usage. There is no need for new users to be trying to
figure
out if they need these features, in my opinion.
The whole WRITING PLUGINS sections could
Hi,
It is unfortunate that it needs to be implemented using the prerun
hook, but I can see your reasons for not rewriting the 'run' method in
CGI::Application.
This module also shows a very good example of the potential usefulness
of the callbacks patch as well.
I updated the AutoRunmode plugin to
Owain wrote:
Drew and Cees,
I am in the process of converting over a non CGA application to run under
CGA. (Sort of) does the same stuff as CGA in a non-OO way. My application
has implemented user and group authentication and this is what I try to
accomplish from a design perspective.
Run mode
Jason Purdy wrote:
I was searching through the list archives and I cannot find a mention
(besides this guy[1] asking and not getting a response (to the plugin
question)) of why we should change our code from C:A:ValidateRM to
C:A:P:ValidateRM. I've heard lazy loading thrown around, but I'm not
Michael,
I originally thought rm-level auth was a bad idea since you should group
the run modes into an application module that is used by the same type
of user. I can however see why you might want to group several run modes
that deal with the same data type together... but I'm still not
Steve Comrie wrote:
I originally thought rm-level auth was a bad idea since you should group
the run modes into an application module that is used by the same type
of user. I can however see why you might want to group several run modes
that deal with the same data type together... but I'm still
Thilo Planz wrote:
At the moment, the callback interface is a little verbose, you have to
first use the module, and then install the callbacks.
Maybe if callbacks and plugins become popular, we could come up with
something more concise, for example
sub setup{
my $self = shift;
While recognizing that tmtowtdi, this is how I deal with situations like
the above...
Using CGI::Application::Dispatch I would have a urls like these
/app/reports/general
/app/reports/download
/app/reports/detail
/app/reports/geo_plot
So even if they were all in the same module, my
On Fri, 29 Oct 2004 16:31:40 +1000, Cees Hek [EMAIL PROTECTED] wrote:
Hi Drew,
I have been hinting at an Authentication plugin for a while now, but
haven't finished it yet. I did a little bit more work on it
yesterday, but I don't have any docs, or any tests written for the
module yet.
On Fri, 29 Oct 2004 09:46:33 -0400, Michael [EMAIL PROTECTED] wrote:
Owain wrote:
Now, this is where I definitely disagree. It's so easy for me to use
mod_perl authentication (especially using C::A::P::Dispatch). You can be
as granular or as top-level as you want. I just don't understand the
On Fri, 29 Oct 2004 11:43:34 +0100, Owain [EMAIL PROTECTED] wrote:
Run mode level authentication is preferable otherwise in your example it
looks like you would need separate your non-authenticated run modes out into
another CGA module (+ instance scripts etc) even though they are just a
On Fri, 29 Oct 2004 08:45:31 -0400, Jason Purdy [EMAIL PROTECTED] wrote:
Also, when it comes to user authentication, when I dabbled in that, I
came across Apache::AuthCookie[2], which in my opinion is a GREAT way to
handle user auth. It separates the whole authentication code away from
your
- Original Message -
From: Michael [EMAIL PROTECTED]
To: Jonathan Mangin [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 3:08 PM
Subject: Re: [cgiapp] [OT] Multiple constraints on field (DFV)
Jonathan Mangin wrote:
Is it possible to put multiple constraints on
On Fri, 29 Oct 2004 10:25:59 -0400, Michael [EMAIL PROTECTED] wrote:
While recognizing that tmtowtdi, this is how I deal with situations like
the above...
Using CGI::Application::Dispatch I would have a urls like these
Interesting module. I've looked at it in the past but will investigate
Drew Taylor wrote:
On Fri, 29 Oct 2004 09:46:33 -0400, Michael [EMAIL PROTECTED] wrote:
Owain wrote:
Now, this is where I definitely disagree. It's so easy for me to use
mod_perl authentication (especially using C::A::P::Dispatch). You can be
as granular or as top-level as you want. I just don't
You know, I was talking with a friend of mine about this sort of thing
the other day, because I was working on an auth scheme for a project
of mine, and wanted some way of making it as pluggable as possible, as
far as permission storage backends go.
It is quite possible that the language I am
The uploaded file
CGI-Application-Dispatch-0.03.tar.gz
has entered CPAN as
file: $CPAN/authors/id/W/WO/WONKO/CGI-Application-Dispatch-0.03.tar.gz
size: 6283 bytes
md5: 359c581028d7bb24a5ffc2cad046626e
changes in this release include:
- fixed build on some systems
- minor optimizations
Guru's
I have a C::A application where I'm using radio_group method for a form.
When the form is displayed, the first option is selected by default. I want
to change this behavior and no option should be select by default.
How can I make this change? Setting -default = is not getting me the
On Fri, 2004-10-29 at 16:36, Drew Taylor wrote:
On Fri, 29 Oct 2004 11:43:34 +0100, Owain [EMAIL PROTECTED] wrote:
Run mode level authentication is preferable otherwise in your example it
looks like you would need separate your non-authenticated run modes out into
another CGA module (+
sub setup{
my $self = shift;
$self-use_plugin('::AutoRunmode');
}
where use_plugin() would use the plugin and call some install
method to let it set itself up.
I like the idea of making it less verbose. I haven't actually looked
at the callback implementation, but is it not possible to
24 matches
Mail list logo
