Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-08-09 Thread Tomas Doran
] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release On 2 Mar 2011, at 15:08, Pedro Melo wrote: Is this a documented change that I missed or a bug? Could we possibly be talking about this method: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits/Catalyst-Runtime.git

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-08-08 Thread John Napiorkowski
- Original Message - From: Tomas Doran bobtf...@bobtfish.net To: Pedro Melo m...@simplicidade.org Cc: The elegant MVC web framework catalyst@lists.scsys.co.uk Sent: Saturday, August 6, 2011 10:47 AM Subject: Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-08-07 Thread Tomas Doran
On 2 Mar 2011, at 15:08, Pedro Melo wrote: I've just tested my app with the this version. I've noticed a small difference with Catalyst::Test. The latest stable version include two headers, 'host' and 'https'. They are missing from this version. Is this a documented change that I missed or a

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-04 Thread Nigel Metheringham
On 3 Mar 2011, at 18:28, Fernan Aguero wrote: Although it was not clear in any of the Plack/PSGI documentation that I've read, my guess is that only framework developers care about this. I, as a developer of web applications, shouldn't. Right? You should care in that it simplifies your

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-04 Thread Tomas Doran
On 3 Mar 2011, at 18:28, Fernan Aguero wrote: In other words, my apps will still work without modification under mod_perl2/Apache whenever the next Catalyst release (5.9, native PSGI) is out. Right? Yes, you should have to make exactly no changes, and everything should continue to work

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-03 Thread Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
Fernan Aguero ✍: what plack/psgi is and/or why I should care I hear that often, so here's the elevator pitch I'm usually telling to convey the basic idea. Catalyst is a Web framework that runs on several Web servers. The different parts necessary to make this work are separated out into

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-03 Thread Dave Rolsky
On Thu, 3 Mar 2011, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: Apart from less code for each framework, there is the other advantage that adding support for a new Web server (e.g. Plack::Handler::Mongrel2) automatically enables this Web server for any PSGI-compliant framework. While it has been possible to run

[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Florian Ragwitz
Hi It gives me great pleasure to announce the third development release of the next major version of Catalyst. The changes from the previous PSGI development release include fixes for various test failures as well as refactoring of the API for retrieving PSGI application code references for

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Pedro Melo
Hi, On Wed, Mar 2, 2011 at 10:50 AM, Florian Ragwitz r...@debian.org wrote: 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

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Tomas Doran
On 2 Mar 2011, at 15:08, Pedro Melo wrote: Is this a documented change that I missed or a bug? A bug! Thanks for trying and notifying us :_) Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo:

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Pedro Melo
Hi, On Wed, Mar 2, 2011 at 3:17 PM, Tomas Doran bobtf...@bobtfish.net wrote: On 2 Mar 2011, at 15:08, Pedro Melo wrote: Is this a documented change that I missed or a bug? A bug! Thanks for trying and notifying us :_) No problem. I'm following the psgi branch, so I can update it and try

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Florian Ragwitz
Many thanks for testing this release. Pedro Melo m...@simplicidade.org writes: I've noticed a small difference with Catalyst::Test. The latest stable version include two headers, 'host' and 'https'. They are missing from this version. Is this a documented change that I missed or a bug?

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Pedro Melo
Hi, On Wed, Mar 2, 2011 at 3:27 PM, Florian Ragwitz r...@debian.org wrote: Pedro Melo m...@simplicidade.org writes: I've noticed a small difference with Catalyst::Test. The latest stable version include two headers, 'host' and 'https'. They are missing from this version. Is this a

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Florian Ragwitz
Pedro Melo m...@simplicidade.org writes: On Wed, Mar 2, 2011 at 3:27 PM, Florian Ragwitz r...@debian.org wrote: I'm not sure if this change of behaviour is something we should fix though. The engine knows that a request is secure by checking psgi.url_scheme, and applications can ask for that

Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release

2011-03-02 Thread Fernan Aguero
On Wed, Mar 2, 2011 at 7:50 AM, Florian Ragwitz r...@debian.org wrote: Hi It gives me great pleasure to announce the third development release of the next major version of Catalyst. [...] You shouldn't have to do _anything_ to upgrade to the new release, other than ensure your application