On 3/27/2011 12:22 PM, Tomas Doran bobtfish-at-bobtfish.net |Catalyst/Allow to
home| wrote:
And I would say that sending an email is a state change, and behavior of the application
domain here.
That's a stretch, because you can argue that any side-effect is a change of state to the
universe
Where is Content-Type being set?
I'd like to send it instead as application/xhtml+xml, if the Accept header of the request
claims to take that. I found this example of rewriting it in Apache, but it would be far
easier to target the necessary pages, not to mention more elegant, if I did this
On Mon, 2011-03-28 at 08:12 -0500, John M. Dlugosz wrote:
Where is Content-Type being set?
I'd like to send it instead as application/xhtml+xml, if the Accept header of
the request
claims to take that.
Catalyst::View::TT::XHTML
Regards,
Denny
signature.asc
Description: This is a
I want to be able to setup a configuration variable in my Catalyst config
that will then be set as the value for one of my model's class variables.
I have a model that will want to use a base path to store some files, However
the Model doesn't know how to access Catalyst and so it can't get the
On Mon, Mar 28, 2011 at 6:49 PM, Derek Wueppelmann dwuep...@gmail.com wrote:
I want to be able to setup a configuration variable in my Catalyst config
that will then be set as the value for one of my model's class variables.
I have a model that will want to use a base path to store some files,
I don't understand why
|Catalyst::Plugin::Unicode::Encoding|
is necessary, based on the writup: it takes request arguments and converts them from
whatever they came in to Perl's native encoding, and likewise for the response.
But Perl is using UTF-8 in its strings anyway. So what's it have
El 28/03/11 19:50, John M. Dlugosz escribió:
I don't understand why
|Catalyst::Plugin::Unicode::Encoding|
is necessary, based on the writup: it takes request arguments and
converts them from whatever they came in to Perl's native encoding,
and likewise for the response.
But Perl is using
On Mon, Mar 28, 2011 at 7:50 PM, John M. Dlugosz wxju46g...@snkmail.comwrote:
I don't understand why
Catalyst::Plugin::Unicode::Encoding
is necessary, based on the writup: it takes request arguments and converts
them from whatever they came in to Perl's native encoding, and likewise for
On 3/28/2011 1:25 PM, Jorge Gonzalez jorge.gonzalez-at-daikon.es |Catalyst/Allow to home|
wrote:
Did you set ENCODING = 'utf-8' in the configuration of your TT View?
Ah, thanks! That worked. I looked again carefully at
On Monday, March 28, 2011 12:50:00 PM John M. Dlugosz wrote:
I don't understand why
|Catalyst::Plugin::Unicode::Encoding|
is necessary, based on the writup: it takes request arguments and converts
them from whatever they came in to Perl's native encoding, and likewise
for the response.
10 matches
Mail list logo