[dancer-users] Running a bot as a REST webservice

[Pierre M]

Wow !! The code in my first email worked, the bot IS shared between all
REST calls.

I just needed to run
    plackup bin/app.pl
instead of
    plackup -L Shotgun bin/app.pl
It's the Shotgun option that made my app.pl be re-initialized each time.

No need for a memcache, no need for workers, it just works! Dancer is my
app online, with a state =)

--- Pierre Masci
I check email a couple times daily; to reach me sooner, you can send me a
text message via this page: https://awayfind.com/mascip


On 7 December 2013 11:13, sawyer x <xsawyerx at gmail.com> wrote:

> 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 at 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 at dancer.pm
>> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>>
>>
>
> _______________________________________________
> dancer-users mailing list
> dancer-users at dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20131207/42df6857/attachment.html>