These are chat archives for petabridge/akka-bootcamp

13th
Apr 2015
Mike Coxeter
@mcoxeter
Apr 13 2015 03:10
Hi, I've completed the first six lessons and eager to start the next track. When I use the link at the bottom of the email I'm getting a 404 error. Will the lessons continue automatically?
Mike Coxeter
@mcoxeter
Apr 13 2015 03:18
Thanks, I've got the next lesson now!
Thomas Tomanek
@thomastomanek
Apr 13 2015 07:22
@Danthar This is actually over MassTransit using RMQ as the transport. I haven't had chance to look into it yet and to see whether MT supports this.
Arjen Smits
@Danthar
Apr 13 2015 07:23
hmm MassTransit has pretty high abstractions. Not sure if they allow these kind of things. I switched from NServiceBus to MassTransit to EasyNetQ
Thomas Tomanek
@thomastomanek
Apr 13 2015 07:30
This is true. Not seen EasyNetQ
Probably talk to the MT guys, although they're pretty busy on V3 atm, so anything prior to that doesn't get much of a look in these days
Arjen Smits
@Danthar
Apr 13 2015 07:32
Has the same abstractions then MassTransit, except for the commandbus, but allows for easier access to lower level rmq stuff.
Yeah they are changing stuff up in v3. Full async support and whatnot.
Arjen Smits
@Danthar
Apr 13 2015 07:43
Although im not sure if you want to go the way that @rogeralsing describes in his gist. Seems that AzureServicebus has a different idea about how to handle message failures. Not Acking a message is a valid application level error scenario. Whereas with the RMQ clients, Ack-ing (or not Ack-ing due to timeout) is an infrastructure level concern, and application level error scenario's should be handled by throwing an exception, which causes the message to go into the error queue. This is from the philosophy that if your message fails to process, its poisoned and any retries should be explicit (in this case, you republishing stuff from the error queue). Sofar iv'e seen all RMQ clients follow this philosophy, at least the .Net clients do.
Ralph Waldenmaier
@wralph
Apr 13 2015 11:17
Hi, I am done with unit 2.5 though the link to get the messages from unit 3 is broken and leads to a 404? How can I subscribe to the next lesson?
Ahh got new mails even with the 404.
Bart de Boer
@boekabart
Apr 13 2015 13:05
"This will be a throwaway token in your account only used for this app. Follow the instructions here and write down your OAuth token."
Not clear what scopes are neede
Arjen Smits
@Danthar
Apr 13 2015 13:08
All the basic stuff. I found the github page where you can create an app-token to be pretty self-explanatory. But basically, it wont need commit access to your repo's or anything. Its just a token so that you can communicate (read-access at the very least) with the github API.
Andrew Skotzko
@skotzko
Apr 13 2015 16:02
@/all those 404 errors and such fixed, sorry about that