[pylons-discuss] Re: problem with deform/ajax..

Further to this, having spent days stepping through javascript, it seems the following is happening, hopefully my description will not be too off the mark. In the example I am using, they use a bit of javascript to 'hook' the ajax form, as follows: // Edit a task when the edit link is clic

Re: [pylons-discuss] advice sought on 'BeforeRender' and 'render' edge case.

It sounds like you'll be interested in subscriber predicates. http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/narr/hooks.html#subscriber-predicates Personally I send emails from message queue in a separate process and so there is no conflict between these rendering environments despi

[pylons-discuss] Re: problem with deform/ajax..

No input at all? that is disappointing. Surely this must be something rather obvious, or something that is missed in the documentation, as it certainly doesnt seem a trivial fix that I can identify. On Thursday, April 24, 2014 3:29:00 PM UTC+12, stua...@gmail.com wrote: > > > Hello. > > I am be

[pylons-discuss] advice sought on 'BeforeRender' and 'render' edge case.

We've run into an annoying edge-case with our use of BeforeRender. Our app utilizes BeforeRender to optimize priming/loading our object cache and data standardization. It's awesome and works great. We recently noticed some odd bugs and a general slowness from caches that weren't primed proper

Re: [pylons-discuss] Re: making the current request available in a debugtoolbar template

this entire package makes so much more sense now. wow. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to

Re: [pylons-discuss] Re: making the current request available in a debugtoolbar template

The `data` variable is generated during the original request. It is then available out-of-band of the original request for use later when `render_content`, `has_content`, `render_vars`, `title`, etc are called. The only methods invoked in-band with the original request are `__init__`, `process_res

[pylons-discuss] Re: making the current request available in a debugtoolbar template

oh! so the panel is generated during the first request (__init__) and attached to the history; then looked up and rendered in the toolbar views ? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receivi

Re: [pylons-discuss] making the current request available in a debugtoolbar template

The toolbar request is the one passed into panel.render_content(request). Anything from the original request should've been put into panel.data (which was generated during the original request). On Wed, Apr 30, 2014 at 5:14 PM, Jonathan Vanasco wrote: > Does anyone have a recommendation for makin

[pylons-discuss] making the current request available in a debugtoolbar template

Does anyone have a recommendation for making the current request (for the debugtoolbar itself) available to custom panel templates ? i just realized that the "request" which is passed along is the original request -- not the request for the debugtoolbar panel. i tried passing into a template

Re: [pylons-discuss] How to store session data server side?

On 04/30/2014 04:36 PM, Michael Merickel wrote: On Wed, Apr 30, 2014 at 3:28 PM, Chris McDonough mailto:chr...@plope.com>> wrote: The presumption that there is a session.id variable won't solve this particular problem, as Bert and Mike have already said. But as a

Re: [pylons-discuss] How to store session data server side?

On Wed, Apr 30, 2014 at 3:28 PM, Chris McDonough wrote: > The presumption that there is a session.id variable won't solve this > particular problem, as Bert and Mike have already said. But as a separate > problem, it could be "solved" if we mandated that a session id be made > available in a com

Re: [pylons-discuss] How to store session data server side?

On 04/30/2014 03:29 PM, Jonathan Vanasco wrote: The focus of this discussion shouldn't be the merits, drawbacks, or implementation details of server-side sessions vs client-side sessions -- which everyone is quick to chime in on. We can talk about that all day. We have, many times.. My concern

Re: [pylons-discuss] How to store session data server side?

On Apr 30, 2014, at 13:29 , Jonathan Vanasco wrote: > […] > This seems to be going in circles. session id is not common across all implementations, doesn’t need to exist for most of them, and thus shouldn’t be relied on. Instead stick your own unique token into the session if you want it. Y

Re: [pylons-discuss] How to store session data server side?

Ignoring everything else for the moment, you've already made yet another assumption that you're not going to be happy about. The raw cookie value is in no way a session identifier. For example in pyramid_redis_sessions the session identifier is cryptographically signed to prevent clients from even

Re: [pylons-discuss] How to store session data server side?

The focus of this discussion shouldn't be the merits, drawbacks, or implementation details of server-side sessions vs client-side sessions -- which everyone is quick to chime in on. We can talk about that all day. We have, many times.. My concern isn't that there is a session_id variable in e

Re: [pylons-discuss] How to store session data server side?

On Apr 29, 2014, at 14:30 , Jonathan Vanasco wrote: > On Monday, April 28, 2014 11:46:22 PM UTC-4, Bert JW Regeer wrote: > What are you using the session ID for? > > Performance logging (session_id into statsd and logs). Unit Testing. > Integrated Testing. Automated Test suites. Development