* Jonathan Rockway <[EMAIL PROTECTED]> [2008-06-20 22:20]:
> >>sub hello_setup : Private {
> >> my ($self, $c) = @_
> >> $c->stash->{setup} = 'done';
> >>}
> >>
> >>sub hello : Private {
> >> my ($self, $c) = @_
> >> $c->forward('hello_setup'); # <-
> >>
On Fri, Jun 20, 2008 at 1:25 PM, Oleg Pronin <[EMAIL PROTECTED]> wrote:
> I use it for 3 years. It might be used in production i think.
> About 5 minutes: there are a set of attributes (ReconnectRetries,
> ReconnectTimeout, etc) - you can manipulate how long it will reconnect.
Thanks for the info
* On Fri, Jun 20 2008, Marc Sebastian Pelzer wrote:
>>> You need a screwdriver, not a hammer.
>>
>>sub hello_setup : Private {
>> my ($self, $c) = @_
>> $c->stash->{setup} = 'done';
>>}
>>
>>sub hello : Private {
>> my ($self, $c) = @_
>> $c->forward('hello_setup');
Hi Marc,
* Marc Sebastian Pelzer <[EMAIL PROTECTED]> [2008-06-20 18:25]:
> I thought that there may be a more elegant way of doing this.
it’s not very nice, no. But at least it works.
Maybe when the dispatcher is finally rewritten :-), forwarding to
the endpoint of a chain and having the entire
I use it for 3 years. It might be used in production i think.
About 5 minutes: there are a set of attributes (ReconnectRetries,
ReconnectTimeout, etc) - you can manipulate how long it will reconnect.
2008/6/20 Mitch Jackson <[EMAIL PROTECTED]>:
> > You can use DBIx::Class with DBIx::RetryOverDisc
> You can use DBIx::Class with DBIx::RetryOverDisconnects as DBI handle and
> you will never got db server away message (it will reconnect as long as
> required until database is up and no queries and transactions will be lost).
Looks cool, but it's got a big warning on it saying it's not stable
f
On Friday 20 June 2008 12:20:49 Gavin Henry wrote:
> 2008/6/20 Buchan Milne <[EMAIL PROTECTED]>:
> > In our internal management web app (which has only been feasible due to
> > Catalyst), we authenticate against our OpenLDAP (2.3) infrastructure.
> >
> > Due to various security requirements (SAOX e
You need a screwdriver, not a hammer.
sub hello_setup : Private {
my ($self, $c) = @_
$c->stash->{setup} = 'done';
}
sub hello : Private {
my ($self, $c) = @_
$c->forward('hello_setup'); # <-
$c->res->body('hello! setup is ' . $c->stash->{setup});
* Marc Sebastian Pelzer <[EMAIL PROTECTED]> [2008-06-20 14:10]:
> I'd like to forward and/or detach to private actions which
> should be chained together, like:
>
> sub hello_setup : Privat Chained {
> my ($self, $c) = @_
>
> $c->stash->{setup} = 'done';
> }
>
> sub hello : Private Chained('hel
Hello,
I'd like to forward and/or detach to private actions which should be
chained together, like:
sub hello_setup : Privat Chained {
my ($self, $c) = @_
$c->stash->{setup} = 'done';
}
sub hello : Private Chained('hello_setup') {
my ($self, $c) = @_
$c->res->body('hello! setup is
2008/6/20 Buchan Milne <[EMAIL PROTECTED]>:
> In our internal management web app (which has only been feasible due to
> Catalyst), we authenticate against our OpenLDAP (2.3) infrastructure.
>
> Due to various security requirements (SAOX etc.), we are required to have
> password expiration etc. So,
In our internal management web app (which has only been feasible due to
Catalyst), we authenticate against our OpenLDAP (2.3) infrastructure.
Due to various security requirements (SAOX etc.), we are required to have
password expiration etc. So, we implemented password policies a while back
usin
12 matches
Mail list logo
