I'm not sure if the object is pickle-able (it has some SA objects in
it), and even if it could it would sometimes be kind of large for
hidden form fields or storing it in a cookie.
And for a session, do I understand correctly that if the user had
multiple instances of a form open in different tabs they would all
share the same session? So the next form submitted would get the
session info for the most recent form rendered, which may not be the
right one. Is that right or have I misunderstood sessions? I've been
reading the documentation but haven't found anything to clear this up.
Thanks for the help.
On Sep 7, 8:13 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote:
> The form display and the form submission are two separate requests.
> 'c' and 'request' are local to the request. There are four ways to
> make data available to the submission request.
>
> - Pass it as hidden form fields.
>
> - Put it in the session in the first request and read it in the second
> request. This is good for data you don't want the user to see
> directory, or that is large. The second request should use
> 'session.get("the_key")' in case the data isn't there; i.e., if the
> form was never requested.
>
> - Pass it in a cookie. This is the most complex way unless you're
> familiar with setting cookies directly.
>
> - Store it in the database keyed by the session ID. This is
> essentially the same as storing it in the session.
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---
