On Fri, Aug 27, 2010 at 12:13 PM, Mike Orr <[email protected]> wrote:
> On Fri, Aug 27, 2010 at 12:51 AM, waugust <[email protected]> wrote:
>> Basically what I wanted to do is have a "Action" model with a action
>> attribute to store a call to a controllers action in order to execute
>> on demand during a procedure later (and in steps), if that makes more
>> sense?

Is this for something like a cron job? If so, "paster request" will
invoke whatever URL you give it, without a server. This is useful if
the action has side effects like expiring old sessions or updating
indexes, which you want to invoke every so often.

Otherwise, why would you want to store an action and call it later?
That sounds like what you really want is a side effect or core
behavior of the action, without all the Pylons request stuff around
it. If so, that could should be factored out into an ordinary function
so that it can be called directly.

-- 
Mike Orr <[email protected]>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to