Just a quick summary of what I found to be useful (though I don't yet
use new Pylons)
Flash Messages. It solves issues of 'c' being too transient, and
session scope being too wide.
T.
--
_i__'simplicity_is_the_key'__tomasz_nazar
_ii'i_am_concern_oriented'JKM-UPR
Tomasz Nazar wrote:
On 8/24/07, *Christoph Haas* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
As I understand 'c' is always reset before any controller's
action - what is
not fun for me, as in my app one user request/click is often 2
(or more)
Pylons
On 8/25/07, Jose Galvez [EMAIL PROTECTED] wrote:
Tomasz Nazar wrote:
On 8/24/07, Christoph Haas [EMAIL PROTECTED] wrote:
As I understand 'c' is always reset before any controller's action -
what is
not fun for me, as in my app one user request/click is often 2 (or
more)
On Fri, Aug 24, 2007 at 02:33:07PM +0200, Tomasz Nazar wrote:
Whatever variable attached to 'c', it is available in the template when
rendered via 'render_response('x.tmpl')'.
I often however use redirects 'h.redirect_to(another_action)' to reuse
controller's code. And the 'c'-attached
Hi there!
Whatever variable attached to 'c', it is available in the template when
rendered via 'render_response('x.tmpl')'.
I often however use redirects 'h.redirect_to(another_action)' to reuse
controller's code. And the 'c'-attached variables are not present in the
redirected template.
As I
As I understand 'c' is always reset before any controller's action
- what is
not fun for me, as in my app one user request/click is often 2
(or more)
Pylons controllers' actions, hence http redirects..
Without knowing your application I dare say that this sounds like you
are using
Evert Rol wrote:
As mentioned, I'm using the g variable (removing the attribute when
not needed), not session. Which one would be better? Is g perhaps
tied to the application, ie if multiple users use it, they all use
the same g variable, but session is still (browser/ip-address) user-
