It's the same thing, IMHO. It's a state. Keeping it in Memcached, token in a cookie, external service, etc. Whichever one you find comfortable is the best. :) On Fri, Dec 6, 2013 at 9:29 PM, Pierre M <piemas25@gmail.com> wrote:
I'm not loving the idea of storing a 3rd party session token, it's a bit of a pain to pass it around and it's not really scalable. Caching the bot itself between each REST request works, but I came accross a possibly nicer idea:
My bot could be running in a Gearman worker, and I would give orders with a Geaman client. Possibly with Dancer::Plugin::GearmanXS, if I used Dancer instead of Dancer2.
It looks the tool for the job. I'll try it in two weeks, when I'm back from holidays.
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users