Hi,
Thank you for the suggestion! I also got a backchannel reply that one could
simply put the swagger map in a (when dev-mode? {:swagger {...}}) form. For
some reason I though that wouldn't be possible because api is a macro but
that actually works fine.
Thanks,
Brjánn
On Thu, 21 Feb 2019 at
Hi,
I'm trying out compojure-api and have included swagger.ui in my api:
(api
{:swagger {:ui "/swagger-ui"
:spec "/swagger.json"
:data {:info {:version "1.0.0"
:title "Title"
...)
However, I don't want swagger to be
> If I was building a system like the one you describe for real, then the
> first tool I'd reach for would be a email sending service, like Mailgun,
> Sendgrid, or AWS SES. These sorts of services take care of queuing mail,
> retrying on failure, and keeping track of mail bounces. They also all
Hi Erik,
It hadn't even crossed my mind that I could write a separate app which is
trigged by cron. I will consider that! I have searched for different
schedulers and found a few options but cannot locate any in Juxt's github
repositories. I've read about transducers and think that I've got a
>
> Thanks for pointing out the submit function and explaining the wrapper.
>> Would you specifically advise against sending the result back through a
>> channel?
>>
>
> It depends what you're trying to do. What are you doing with the result,
> and what's your reasoning for not handling it in your
unning / not running) is stored in an agent to
> avoid race conditions (i.e., starting multiple threads or not starting a
> thread because it is running when its status is checked but stops right
> after).
>
> My code is here
> https://gist.github.com/brjann/2aef16849b9bd445374cb6b31ef
It seems that I somewhat over-engineered my queue :-) I don't know any Java
so this is very helpful!
If I want to know the result of the email send within the worker
thread, would you recommend sending it back through a channel?
One purpose of my queue was to be able to put urgent messages at
- All messages should be sent async, i..e, the web user should not have
>>>> to wait while the email is being sent. -> I'm sending them in a separate
>>>> thread.
>>>> - I have a fear that if I have a thread dedicated only to sending
>>>> emails, I'm wa
ally consists of
>> - An eternal go loop that receives a notification through a channel if
>> new messages have been queued
>> - The go loop checks if the mail sender thread is running. If not, it
>> starts it.
>> - The mail sender thread dies 5 secs after the last email w
ithub.com/brjann/2aef16849b9bd445374cb6b31efece60
If any of you have had the time and energy to read this far (including the
code), I would be very grateful for your input.
- Is there a risk that my go block will hang?
- Have I eliminated the risk for race conditions?
- Do I really need to kill t
10 matches
Mail list logo
