13

I'm trying to explain to this dumb mf-er why we can't use send data simply.
It's a mobile platform I said, you can't rely on having network I said, the dumbass users might try it on 2% battery I said.
DO'H BUT MY INTERZ CAN DO IT IN 5 MINUTES.
Yeah, enjoy crashing the app with asynctask like a stupid bitch. When it fails under nearly every possible condition that deviates from the ideal, you can go write down how great your interns are, eat it up, shit it out and when you grow a flower from that, then I might help you again.
Retard server people.

Comments
  • 0
    If not with an asynctask (lets assume okhttp is an asynctask), how else would you post data on a server
  • 2
    Also hi welcome to devrant
  • 4
    @BindView okhttp is one level of abstraction below what you'd want to use.
    Something like Retrofit is what you'd use, backed by a JobScheduler job written to retry with a backoff if it fails to actually initiate this (also only trying when the right kind of network i.e mobile data or wifi depending on task, is available).
    So your task is persistent through reboots, retries automatically and appropriately, and happens in the background in safe way.
  • 1
    @BindView thanks! I like ur name.
  • 1
    Haha thanks, people always tag me as blindview tho.

    Yeeeah i dont like retro, id rather use volley but thats just my quirk. Whats your opinion on using rxandroid for api calls? I found it really responsive.
  • 0
    @BindView I'd only used volley once a long ago for image loading. Retrofit has since surfaced as a more modern library for network calls.
    I haven't really used Volley enough to comment on how it is as a library, though it is deprecated now so meh.
    Oh, I didn't know there was a way to do it directly with rxandroid, thanks for the tip!
Add Comment