Absolutely, However, I think you missed the gist of my point. I was not suggesting you code with reckless abandon, expecting things will always go as expected.
Let me detail out the reasoning behind my post: 1.) Rhapsody's service is the only service I ever have any difficulty out of. 2.) Rhapsody doesn't always work properly in their native client 3.) Other friends/family report similar issues with Rhapsody's service 4.) Users of other devices report similar problems interfacing with Rhapsody. Do we see a pattern forming yet? It's probably reasonable to assume that at least some effort has been put into "defensive coding" due to the fact that those other services are likely not 100% reliable either, yet for the most part they work very well. Perhaps the team just completely drop the ball on only Rhapsody? That is certainly a possibility, but the evidence we do have does not point that way. I wasn't suggesting that any efforts to improve the interface be stopped - I was suggesting, however, that as a developer, at some point you have to again decide when you are going stop complicating your code and expending your resources trying to resolve issues not under your control. You have, at this point put forth a reasonable effort and must move on to dealing with things you can control. Putting in "fixes" as suggested by the OP seems like it would be counter productive - handing unexpected errors is one thing - trying to predict the various failure modes of an unpredictable system and counter them undocumented, trial & error methods that will likely lead to more complex, difficult to maintain, and bug prone code is quite another. -- 86atc250r ------------------------------------------------------------------------ 86atc250r's Profile: http://forums.slimdevices.com/member.php?userid=15476 View this thread: http://forums.slimdevices.com/showthread.php?t=63462 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
