My web app grabs data via API routes, populates a form with it from which users select options, and upon submission of the form sends off some emails. I don't need to store data anywhere as the API routes give me access to the most up-to-date information, so it sounds like client-side storage would work best. The most essential piece I can see for storing any session data at all is to confirm the user's credentials for passing requests to the API routes.
Is the signed cookie session factory <http://docs.pylonsproject.org/projects/pyramid/en/latest/narr/sessions.html#using-the-default-session-factory> okay for production use if implemented with encryption? On Friday, May 15, 2015 at 1:06:23 PM UTC-5, Jonathan Vanasco wrote: > > pyramid_redis_session requires storing sessions on a redis server... so > you need to install redis on your machine AND create a database/password on > redis. > > redis is a GREAT solution for managing server-side session data. if you > don't need to store data server side though (because it is very small, or > does not need to be shielded from the public), pyramid supports client-side > session data in the form of signed cookies (i think there are encrypted > cookies in the base too). > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
