Hello, In Larrys code I guess the auth happens when the user tries to run a workflow. If the run is accepted by the player then the credentials must have been correct. I would not get too worried about handling all errors.The main thing is that the user can run a workflow, improve the error handling later. I think we have always made the assumption that the user gets their username and password correct (I know, never assume).
Cheers, Ian On 2 September 2016 at 16:08, Donal K. Fellows < [email protected]> wrote: > On 02/09/2016 15:14, Stian Soiland-Reyes wrote: > >> but what about proper handling of headers, caching and >> authentication >> > > HttpURLConnection does some of those. Allegedly. I don't like how it does > auth, but you can override if you know that the host will require it, which > is usually the case for API access. It's the API access use-case that I > believe is of greatest interest to us, yes? > > It certainly does connection sharing via keepalive handling, and you can > set any headers you want, a fact I've used quite a few times. Also, with > API access you typically don't want caching in the first place; we're not > writing a web browser, we're accessing web services. > > Donal. >
