I am a new Django person as well. There is one other point about
storing data in sessions. If you expect the site to grow you should
put the session data in a back-end database. This will allow multiple
servers to access the data. This is important if you ever want to have
load balanced servers wh
Thank you Andrew, very interesting.
In case of using sessions, maybe it.s possilbe to create an object to
serialize only the data, the same as the hidden fields do. So this way
we can solve a problem,
Example: form = MyForm( serialized_data ) where serialized data is a
dictionary get by form.clean
I believe the general best practice is that sessions should be viewed as
a last resort for storing data.
You can store data in a number of places and they each have their
benefits and drawbacks.
The easiest place to store data is the URL, but storing user-specific
information in the URL is a
On 7 jun, 00:05, Grupo Django <[EMAIL PROTECTED]> wrote:
> Hi! Just a simple question.
> The Form Wizard application stores the data hashed in hidden fields.
> Why not in a session? Why is it better? I just want to learn best
> practices.
>
> Thank you.
Another question :-)
Can you get back to re
Hi! Just a simple question.
The Form Wizard application stores the data hashed in hidden fields.
Why not in a session? Why is it better? I just want to learn best
practices.
Thank you.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
5 matches
Mail list logo
