[Pianod] mobile application already working, request comments on track status changes

[Michael R. Hines]

Oh, no, there's nothing wrong on the Pianod side - it's the app itself
that's not responding - I'm not checking for all the status codes and in
some cases I'm sending multiple requests to Pianod simultaneously when I
should not =).

But yes, do try Titanium - you'll love it. They have excellent
documentation.

Regarding the status code questions:
- Code 106 (from a UI perspective) would still be treated the same as
103: The reason is that if a song stops, a new song has to be chosen
regardless whether the user likes it or not (even if the new song comes
from the same station or the same playlist). As a result, the UI throws
the user back to the list of stations so that they can confirm whether
or not they want to continue with the same station or choose a new
one..... I'm not sure the new code would be all that utilized.....

- Code 101/102: .... I agree with your obersvation: In my client
programs, I'm treating 101, 102, and 104 as all essentially a part of
the same block of information, regardless whether or not they are unique
- meaning they are parsed as the same logic, regardless whether the
station is stopped or playing.... I'd say the choice is yours - if you
remove them (or unify them) - it would certainly save a few lines of
code in client programs....

- Code 109: Same answer as 101/102 (and 104) - I would parse 109 in the
same logic path in the client as the others, regardless of the new
syntax.

- Michael

On Sun, 2012-12-09 at 18:58 -0500, Perette Barella wrote:

> The behavior Peter described suggests it's stuff in the main thread, which would mean it's delaying while getting a new playlist or something like that.  I've seen it do that rarely; it eventually continues when the request times out.  It's rare enough for me I've chalked it up as network or Pandora server dropouts.
> 
> I have also seen playback hang in the middle of a song, while the UI stays responsive, but that's also traceable to network... and it also times out and recovers in a bit.
> 
> 
> 
> As far iOS compiling... I downloaded Titanium, now I need to learn how to use it in my copious spare time :) .  Sounds like you guys are rocking on it though.
> 
> 
> 
> Rethinking of reworking a couple of track status codes because there's some conflation.  Particularly:
> 	103 Playback is stopped.
> 
> This is ambiguous in that there may or may not be a station selected.  Thinking of breaking out/adding 106 (Stopped, no station) to distinguish from 103 (Paused intertrack, station selected).  Thoughts?
> 
> 
> 
> Also, formatting for 101/102 playback status messages is way too busy and confusing:
> 	101 now/length/remain Playing {mix|station} selected-station-name
> 
> Unfortunately, this conflates selected-station with current-track.  Thinking of adding
> 	109 {Mix|Station}: selected-station-name
> 
> There's also the question of whether (and for how long) to retain 101/102 as-is for legacy support.  Thoughts?
> 
> 
> Perette
> 
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20121209/84653912/attachment-0003.htm>