[Catalyst] Accesing PSGI 'env' from in a controller

Answering my own question here..
Stuff was hidden in:

$c->engine->env->{...};

I know this isn't very portable, but it's for an internal app where
being able to pass some extra info through from the plack middleware
will be very helpfu.

I'm curious though - How would you suggest such stuff is handled?

cheers,
Toby

Hi,

I guess the "right" way to deal with this would be to wrap that code in
a component which you'd later use from your Catalyst app, thus
decoupling them and keeping your code portable.

For example, that's what Catalyst::Plugin::Session::PSGI aims to do. You
access the session as usual and the "dirty" details are handled by the
plugin and its config.

cheers,

Catalyst::Plugin::Session::PSGI has worked in the cases I've tried, which
shouldn't be surprising as I wrote the module to meet my own requirements.
:)

I've flagged this module as experimental because I know there are a couple
of places where I've probably abused or misunderstood the best way to solve
the problem I had. I'm worried that there are sharp edges and stupid bugs in
places I simply haven't considered yet.

I'm always happy to receive feedback, constructive criticism and patches on
my modules and I'd really like to get some feedback, better solutions and
tests so that I feel more comfortable dropping the experimental warning in
the future.

Chiz