Thanks for everyones help. I'm going to go with the subroutine for now.
This is all the app does, download a file, manipulate it, then serve it up for pick up. It does the download and manipulate action once a day, and the upload happens once a day. We've got raven emailing us if anything goes wrong. If the download, file manipulation or http server fails, then we'll know about it. If any of the first two jobs stop for any reason, and then stop the file server, that's not a bad thing in this instance, as we wouldn't want the other side picking up the file. I don't see the solution being in place as a permanent one, moving data around in files like this these days seems a bit archaic. We'll be looking into putting some resource into using the some of the API's form the 3rd parties involved pretty soon. Thanks again to everyone who's replied, I learnt some stuff for sure! On Wednesday, 7 September 2016 16:43:31 UTC+1, Matt Davies wrote: > > Evening all > > We're writing a new app and we'd like it to do a number of things at the > same time. > > We're planning on using gocron https://github.com/jasonlvhit/gocron to > schedule grabbing some files from another source, then reformatting those > files and placing them into a folder in the app. > > That's all working fine. > > What we now need to do is serve those file up from that folder all of the > time using http.ListenAndServe. > > Am I on the right track here? > > https://tour.golang.org/concurrency/1 > > Or maybe gocron can schedule the http.ListenAndServe to run all the time? > > Any tips or advice greatly appreciated. > > > > > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
