[01:37] <rick_h_> just love this one https://plus.google.com/116120911388966791792/posts/Q8kNRCSiBoR
[02:07] <brousch10> beautiful
[02:10] <rick_h_> yea, 5 pretty minutes in a day of drizzle crappiness
[13:13] <cmaloney> Good morning
[18:14] <rick_h_> hello from the plane because I forgot to pull my code down to work on
[19:29] <cmaloney> Hello from home, where we finally are after taking J's dad back to emergency
[19:31] <cmaloney> He's fine, but they are keeping him over night
[20:35] <derekv> i'm watching this video on the proper way to implement a rest client on andriod
[20:36] <derekv> its informative but, seems way overly complex
[20:36] <derekv> he's suggestly like 7 layers
[20:36] <derekv> suggestly heh
[20:36] <derekv> suggesting even
[20:51] <waf> is he going full HATEOAS? (like following "link" attrs to build client intelligence)
[20:52] <derekv> hemm idk
[20:53] <derekv> 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] <derekv> 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] <derekv> the processor is called by a service
[20:54] <derekv> the service is a seperate process from the app, and you have to communicate via intents and bundles and crap
[20:54] <derekv> which is a big pita so you should have a service-helper in your app that helps with communicating with the service
[20:55] <derekv> meanwhile the processor mirrors its activities to a content provider which can provide a cursor to any subscribed activities
[20:55] <derekv> leik
[20:58] <derekv> 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] <derekv> if
[20:59] <derekv> hmm, your putting a row in the table to represent the state of a rest call
[20:59] <derekv> 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] <derekv> but... either you have a live thread doing the call or its moot
[21:00] <derekv> i suppose you might be interested that the call failed.
[21:01] <derekv> I get it, but it screams to me that there is a simpler way
[21:03] <derekv> waf: no not hateoas
[23:22] <derekv> random q, anyone have experiance with procurve switches?