[01:37] just love this one https://plus.google.com/116120911388966791792/posts/Q8kNRCSiBoR [02:07] beautiful [02:10] yea, 5 pretty minutes in a day of drizzle crappiness [13:13] Good morning === noogenesis is now known as derekv [18:14] hello from the plane because I forgot to pull my code down to work on [19:29] Hello from home, where we finally are after taking J's dad back to emergency [19:31] He's fine, but they are keeping him over night [20:35] i'm watching this video on the proper way to implement a rest client on andriod [20:36] its informative but, seems way overly complex [20:36] he's suggestly like 7 layers [20:36] suggestly heh [20:36] suggesting even [20:51] is he going full HATEOAS? (like following "link" attrs to build client intelligence) [20:52] hemm idk [20:53] like, the service calls should be represeted by java objects for each entity / call ... and happen on a background thread with callbacks. ok... [20:53] but this should be called by a processor, that puts a row in a db for each entity saying the state of the call [20:54] the processor is called by a service [20:54] the service is a seperate process from the app, and you have to communicate via intents and bundles and crap [20:54] which is a big pita so you should have a service-helper in your app that helps with communicating with the service [20:55] meanwhile the processor mirrors its activities to a content provider which can provide a cursor to any subscribed activities [20:55] leik [20:58] i don't know everytime i hear someone using the term "pattern" i feel like what they should be saying is "someone please provide a library or something so that I can do this thing in my app in a way that is so natural its no longer worth calling it a pattern" [20:59] if [20:59] hmm, your putting a row in the table to represent the state of a rest call [20:59] because the UI that needs that state may or may not exist ATM (but may or may not exist again in the future) [21:00] but... either you have a live thread doing the call or its moot [21:00] i suppose you might be interested that the call failed. [21:01] I get it, but it screams to me that there is a simpler way [21:03] waf: no not hateoas [23:22] random q, anyone have experiance with procurve switches?