incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zachary “Gamer_Z.” Yaro <zmy...@gmail.com>
Subject Re: Permanently running an email client within wiab
Date Sat, 22 Jun 2013 02:21:03 GMT
If we want to make it possible for WIAB to be usable for e-mail, it seems
like it would make sense for *e-mails* sent to user@mydomain.com show up as
*waves* (or replies to waves) for the user@mydomain.com wave account.  That
would presumably mean WIAB would need to have an e-mail server in it too
(preferably designed such that it can be separated from the wave server).
 Then when the mydomain.com e-mail server receives an e-mail sent to a
given user, it could turn that into something to be passed to the wave
server.

I have very limited knowledge of how these things function, but would
something like that work?


—Zachary “Gamer_Z.” Yaro


On 21 June 2013 21:38, Bruno Gonzalez (aka stenyak) <stenyak@gmail.com>wrote:

> Still working on the email bot... I'm at a point where I can correctly
> check for unread emails via IMAP, process their contents, and generate a
> new blip per email.
>
> Customary preview screenshot: http://imgur.com/FI5GTvw
>
> So far so good. The problem is, the only way I can currently receive email,
> is to manually command the bot to check for new emails (i.e. I write
> "bot:recv\n" in any wave where the bot is a participant).
>
> Instead of this, I'd like for the bot to be checking for incoming emails
> automatically (for example, once per minute).
>
> I have absolutely no idea where I should put this functionality, and how.
> The thread would periodically check for emails, and suposedly sleep the
> rest of the time. Another option is for it to be ran every X seconds (maybe
> a cron job?).
> I don't know if there's other recommended way to do this.
>
> At first sight, I could start a thread on the constructor for my RobotAgent
> class (which I believe this would only spawn a single thread in the
> lifetime of the wiab server), and have it run an infinite loop, with a
> "sleep(40s)" after each iteration, or something.
>
>
> Thanks for any hints!
>
>
> --
> Saludos,
>      Bruno González
>
> _______________________________________________
> Jabber: stenyak AT gmail.com
> http://www.stenyak.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message