Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89000-TRIAL PSGI Catalyst - first development release.
On Monday, January 24, 2011 05:12:58 PM Tomas Doran wrote: > Hi > > It gives me great pleasure to announce the first development release > of the next major version of Catalyst. > > This is a development release, and we need people to start trying to > use it _NOW_, and to tell us about the issues you find with your real > world applications. Otherwise we're going to be unable to fix those > issues before a final release. > > There are still some known problems with the current release, and the > upgrading documentation is at this stage anything but complete. > However, we have been working hard to keep this release as compatible > as possible with previous versions, and the documentation for > upgrading will greatly improve before the final version.. > > Known issues: > * -l argument to myapp_fastcgi.pl script is broken (this is already > fixed in subversion) Actually *all* arguments to the _fastcgi script are broken in 5.89000-TRIAL (incl. -l/--listen, -n/--nproc, -d/--detach, -e/--keeperr, and -M/--manager). If you need to launch with the _fastcgi script, you will need to wait for the next trial release, or build from svn (Catalyst-Runtime/5.80/branches/psgi) or at least get Catalyst::Script::FastCGI from there. You can still test with _server.pl though, or with your own choice of Plack server and .psgi file, or test apps with Catalyst::Test and TWMC. If you maintain any modules that interface with Catalyst, give them a quick check to make sure that they don't assume the existence of Catalyst::Engine::CGI -- if they do, they will break with the removal of Catalyst::Engine::* ! Thanks, Andrew ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89000-TRIAL PSGI Catalyst - first development release.
Hi It gives me great pleasure to announce the first development release of the next major version of Catalyst. This is a development release, and we need people to start trying to use it _NOW_, and to tell us about the issues you find with your real world applications. Otherwise we're going to be unable to fix those issues before a final release. There are still some known problems with the current release, and the upgrading documentation is at this stage anything but complete. However, we have been working hard to keep this release as compatible as possible with previous versions, and the documentation for upgrading will greatly improve before the final version.. Known issues: * -l argument to myapp_fastcgi.pl script is broken (this is already fixed in subversion) * lighttpd versions below 1.4.23 are known to be broken (this should be able to be worked around using Plack::Middleware::LighttpdScriptNameFix - we would love some people using earlier versions of lighttpd to help test this) * IIS6 is believed to be broken (fix will be forthcoming - please shout up if you will be able to test this for us). * Alternate engines such as Stomp and Wx are broken (we will be working with the authors to fix these before a final release version) * Two of the tests in the distribution are broken if you install onto a clean system Other than this list of known issues, everything should continue working as it did beforehand for all users (including current users of Catalyst::Engine::PSGI). You shouldn't have to do _anything_ to upgrade to the new release, other than ensure your application scripts (as generated by catalyst.pl) to use the Catalyst::Script:: classes. Please test the release out and let us know how you get on. The release can be found at: http://search.cpan.org/~flora/Catalyst-Runtime-5.89000-TRIAL/ or if you are deploying with fastcgi, you can grab the bugfixed version from subversion at: http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/branches/psgi/ Please report your successes (and/or failures) to the list, or come grab me on irc. We'll be trying to get a new dev release out every couple of weeks now until people stop finding issues.. Thanks in advance t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] progressive authentication via db & LDAP
On 24 Jan 2011, at 15:17, piccard wrote:
Is there a possibilty to map the keys, so they also work for a LDAP-
authentication?
Yes, there is. You'll need to patch the code, but the patch would be
very welcome upstream.
Add an authinfo_remap key to the config, and the code...
if ( my $map = $self->config->{authinfo_remap}->{$realm->name} ) {
foreach my $from (keys %$map) {
$auth->{$map->{$from}} = delete $auth->{$from};
}
}
or something similar... Add a couple of tests to that, and you're done..
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Gearman
On Mon, Jan 24, 2011 at 12:54 PM, Octavian Rasnita wrote: > Hi Devin, > > From: "Devin Austin" > > You might also want to create a job "tracker" that uses a database of > some > > sort to mark jobs done when they complete, and just selects jobs that are > > incomplete and runs them. That way, if a job doesn't complete, the > tracker > > picks it up and sends it to the worker again. > > > > I wrote an Advent article on this: > > http://www.catalystframework.org/calendar/2010/7 > > > > -- > > Devin Austin > > > I read your article and it was very helpful. > The client and worker I made were inspired from those I found in that > article. > > I have also read at the end that Gearman is mainly used for speed and not > for reliability but I thought that this may be because it doesn't use a > permanent database and that the jobs might disappear if the Gearman server > is killed. > However, I see that the jobs disappear even if the server is running fine. > > I think that I actually need a job tracker for making sure the jobs are > done correctly than executing those jobs faster. > > I have also taken a look at Beanstalk but I haven't seen a version for > Windows. > > I don't like the idea to create my own job queue, so if I won't be able to > patch TheSchwartz::Moosified to work with Oracle I think that I will have to > use a MySQL DB only for holding the job queues. > > Octavian > > > ___ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > I neglected to mention that I have written a job tracker *after* writing that article. Source is here: https://github.com/dhoss/Deimos/blob/entry_categories/script/deimos_job_listener.pl It's not *great* code, but the idea is there. -- Devin Austin http://www.codedright.net 9702906669 - Cell ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Gearman
Hi Devin, From: "Devin Austin" > You might also want to create a job "tracker" that uses a database of some > sort to mark jobs done when they complete, and just selects jobs that are > incomplete and runs them. That way, if a job doesn't complete, the tracker > picks it up and sends it to the worker again. > > I wrote an Advent article on this: > http://www.catalystframework.org/calendar/2010/7 > > -- > Devin Austin I read your article and it was very helpful. The client and worker I made were inspired from those I found in that article. I have also read at the end that Gearman is mainly used for speed and not for reliability but I thought that this may be because it doesn't use a permanent database and that the jobs might disappear if the Gearman server is killed. However, I see that the jobs disappear even if the server is running fine. I think that I actually need a job tracker for making sure the jobs are done correctly than executing those jobs faster. I have also taken a look at Beanstalk but I haven't seen a version for Windows. I don't like the idea to create my own job queue, so if I won't be able to patch TheSchwartz::Moosified to work with Oracle I think that I will have to use a MySQL DB only for holding the job queues. Octavian ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Gearman
On Mon, Jan 24, 2011 at 9:33 AM, Bill Moseley wrote: > Octavian, > > There's a Gearman Google Group that might be more helpful for you. > > 2011/1/24 Octavian Rasnita > >> Hi, >> >> I have installed Gearman::Server and ran gearmand under Linux and tried to >> use the worker and the client from Windows, but I saw that Gearman is not >> very reliable. >> >> I have created a worker that sends email but for beeing sure that it is >> not a problem of the mail server I have put it to write a line in the log >> each time it was appealed. >> >> From 10 similar requests, the worker is called only 7 or 8 times. >> >> I have ran gearmand with no options. >> >> Do you have any idea if this is normal to happen or I am missing some >> important parameters? >> >> Thanks. >> >> --Octavian >> >> ___ >> List: Catalyst@lists.scsys.co.uk >> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst >> Searchable archive: >> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ >> Dev site: http://dev.catalyst.perl.org/ >> >> > > > -- > Bill Moseley > mose...@hank.org > > ___ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > > You might also want to create a job "tracker" that uses a database of some sort to mark jobs done when they complete, and just selects jobs that are incomplete and runs them. That way, if a job doesn't complete, the tracker picks it up and sends it to the worker again. I wrote an Advent article on this: http://www.catalystframework.org/calendar/2010/7 -- Devin Austin http://www.codedright.net 9702906669 - Cell ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Gearman
Octavian, There's a Gearman Google Group that might be more helpful for you. 2011/1/24 Octavian Rasnita > Hi, > > I have installed Gearman::Server and ran gearmand under Linux and tried to > use the worker and the client from Windows, but I saw that Gearman is not > very reliable. > > I have created a worker that sends email but for beeing sure that it is not > a problem of the mail server I have put it to write a line in the log each > time it was appealed. > > From 10 similar requests, the worker is called only 7 or 8 times. > > I have ran gearmand with no options. > > Do you have any idea if this is normal to happen or I am missing some > important parameters? > > Thanks. > > --Octavian > > ___ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ > > -- Bill Moseley mose...@hank.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] progressive authentication via db & LDAP
Hello,
like in the def. guide 2 catalyst described I've tested a progressive
authentication via DB and LDAP, which worked just fine :-D
But now I have to use an already existing DB, which has different
column-names. As long as I authenticate via a DB everything works,
because I can pass the the column-name as keys:
if ($c->authenticate({ user_identification => $username,
user_password => $password } )) {
Unfortunalty the auth-call doesn't work for the LDAP-auth any more.
Is there a possibilty to map the keys, so they also work for a
LDAP-authentication?
Or do I have to duplicate my code and pass the realm, like:
if ($c->authenticate({ username => $username,
password => $password }, 'ldapAuth'
)) {
thanx :-D
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
[Catalyst] Gearman
Hi, I have installed Gearman::Server and ran gearmand under Linux and tried to use the worker and the client from Windows, but I saw that Gearman is not very reliable. I have created a worker that sends email but for beeing sure that it is not a problem of the mail server I have put it to write a line in the log each time it was appealed. >From 10 similar requests, the worker is called only 7 or 8 times. I have ran gearmand with no options. Do you have any idea if this is normal to happen or I am missing some important parameters? Thanks. --Octavian ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Job Queue recommendation
On Mon, Jan 24, 2011 at 5:40 AM, Tomas Doran wrote: > > On 21 Jan 2011, at 15:30, Alexander Hartmaier wrote: > >> t0m created CatalystX::JobServer which is currently only available on > > This entirely requires RabbitMQ (well, any AMQP broker should be fine, but > I've only tried Rabbit) to do the actual queueing. > I would also recommend to try: http://search.cpan.org/~dsnopek/POE-Component-MessageQueue-0.2.10/lib/POE/Component/MessageQueue.pm > Cheers > t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Job Queue recommendation
On 21 Jan 2011, at 15:30, Alexander Hartmaier wrote: t0m created CatalystX::JobServer which is currently only available on This entirely requires RabbitMQ (well, any AMQP broker should be fine, but I've only tried Rabbit) to do the actual queueing. Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
