[Catalyst] Testserver dies under IE - patch

Hi all. This is a small patch that makes the testserver survive Internet Explorer.. This is probably not the correct fix.. since that would be to find out what the problem is.. Somehow it seems that the socket dissapears earlier when IE it in the other end. patch --- /usr/share/perl5/Catalyst/E

Re: [Catalyst] Testserver dies under IE - patch

> Hi all. > > > This is a small patch that makes the testserver survive Internet > Explorer.. This one even works.. --- /usr/share/perl5/Catalyst/Engine/HTTP.pm2006-07-19 23:45:16.0 +0200 +++ lib/Catalyst/Engine/HTTP.pm 2006-10-03 12:02:25.0 +0200 @@ -305,13 +305,14 @@ m

Re: [Catalyst] Configuring Catalyst::Model::DBIC::Schema from YAML

On Mon, 2 Oct 2006, Matt S Trout wrote: > Jon Warbrick wrote: > > But for some reason my Catalyst::View::MicroMason > > view, called Lookup::View::MicroMason _isn't_ successfully configured - it > > behaves as if the extra mixins are not present. Anyone any idea why? > > Yes. Because it's broke

Re: [Catalyst] Testserver dies under IE - patch

On Tue, Oct 03, 2006 at 12:04:15PM +0200, Jesper Krogh wrote: > > > Hi all. > > > > > > This is a small patch that makes the testserver survive Internet > > Explorer.. I don't use IE enough to know for sure, but lately I've fired up an ssh tunnel (on the same machine) to the test server and that

Re: [Catalyst] Testserver dies under IE - patch

> On Tue, Oct 03, 2006 at 12:04:15PM +0200, Jesper Krogh wrote: >>> This is a small patch that makes the testserver survive Internet >>> Explorer.. >>> > > I don't use IE enough to know for sure, but lately I've fired up an > ssh tunnel (on the same machine) to the test server and that seemed to >

Re: [Catalyst] Testserver dies under IE - patch

Jesper Krogh wrote: >> On Tue, Oct 03, 2006 at 12:04:15PM +0200, Jesper Krogh wrote: This is a small patch that makes the testserver survive Internet Explorer.. >> I don't use IE enough to know for sure, but lately I've fired up an >> ssh tunnel (on the same machine) to the test serv

Re: [Catalyst] Configuring Catalyst::Model::DBIC::Schema from YAML

On 03/10/06, Jon Warbrick <[EMAIL PROTECTED]> wrote: > On Mon, 2 Oct 2006, Matt S Trout wrote: > > > Jon Warbrick wrote: > > > But for some reason my Catalyst::View::MicroMason > > > view, called Lookup::View::MicroMason _isn't_ successfully configured - it > > > behaves as if the extra mixins are

Re: [Catalyst] Spending time with Catalyst (slightly OT)

> http://cms.wikia.com/wiki/JavaScript_Libraries > Please fill in the other libraries that I missed. Perhaps this can be of help to some people: http://www.infoworld.com/article/06/07/31/31FEajax_1.html?s=feature -- Med venlig hilsen Kaare Rasmussen, Jasonic Jasonic Telefon: +4

[Catalyst] getting the db connection used by catalyst

if you have a (dbix) database, and use it as a model, you generally end up doing this : $c->model-> and the database connection is handled internally. I now want to write another model which uses the db. It would be better to use the existing connection that cat has created, rather than cre

Re: [Catalyst] getting the db connection used by catalyst

On 10/3/06, Daniel McBrearty <[EMAIL PROTECTED]> wrote: if you have a (dbix) database, and use it as a model, you generallyend up doing this :$c->model-> and the database connection is handled internally.I now want to write another model which uses the db. It would be better to use the existing

Re: [Catalyst] getting the db connection used by catalyst

basically it does some fancy processing on the db and caches the results. initially, that will be it. It will present a number of convenience methods, which can be used to access either the db or cached data. There will likely be some methods to write to the db, again convenience stuff. On 10/4/

Re: [Catalyst] getting the db connection used by catalyst

I assume you have considered adding this to your dbic-schema? If it is all to deal with the same DB, and the same structures, you might benefit from that. andreas On 4. okt. 2006, at 04.27, Daniel McBrearty wrote: > basically it does some fancy processing on the db and caches the > results.