Ah yes, you guys are right, I wrongly wrote "between requests", where it should have been "between routes" :)
On 25 January 2012 00:37, Flavio Poletti <[email protected]> wrote: > On Wed, Jan 25, 2012 at 12:54 AM, damien > krotkine <[email protected]> wrote: >> >> >> There is the 'vars' function to store a state variable between requests. > > > On Tue, Jan 24, 2012 at 8:54 PM, Gurunandan Bhat <[email protected]> wrote: >> >> Thanks Damien. I see now that vars is the best way to go. > > > I'm certainly not as aware of Dancer internals as Damien, but I would think > that this is not the way to go actually. It is my understanding that the > "vars" mechanism more or less boils down to what failed for you, and that > there is absolutely no effort to synchronize the vars across multiple > processes. > > I think David got it right: > >> You should use the 'vars' keyword if you need to share stuff between a >> single request, and use sessions (or e.g. memcached) to maintain state >> between requests. > > > A shared data source - database, memcached, whatever - seems to be the right > choice to save your server-side state. > > Cheers, > > Flavio. _______________________________________________ Dancer-users mailing list [email protected] http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
