[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Audio Control schema changes
- Subject: Re: Audio Control schema changes
- From: Michael McSharry
- Date: Tue, 17 Feb 2004 20:14:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<TITLE>Message</TITLE>
<DIV><FONT face="Arial" size="2">I'll go
with the flow. I'm just jumping in mid-stream without the history
of how the protocol has evolved. My analogy, has to do with the
protocol design rather than with the actual data. Once a load of
apps have been implemented that flood the network then it becomes difficult
to redesign the protocol to make it more efficient because of all of the
legacy implementations.</FONT></DIV>
<BLOCKQUOTE>
<DIV>----- Original Message ----- </DIV>
<DIV><B>From:</B> <A title="lists@xxxxxxx"
href="mailto:lists@xxxxxxx";>Kevin
Hawkins</A> </DIV>
<DIV><B>To:</B> <A
title="xAP_developer@xxxxxxx" href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A>
</DIV>
<DIV><B>Sent:</B> Tuesday, February 17, 2004 10:15
AM</DIV>
<DIV><B>Subject:</B> RE: [xAP_developer] Audio Control
schema changes</DIV>
<DIV></DIV>
<DIV dir="ltr" align="left"><FONT
face="Arial" color="#0000ff"
size="2"></FONT> </DIV><FONT
face="Arial" color="#0000ff"
size="2"></FONT>
<BLOCKQUOTE dir="ltr">
<DIV class="OutlookMessageHeader" lang="en-us"
dir="ltr" align="left">
<HR tabIndex="-1">
<FONT face="Tahoma"
size="2"><B>From:</B> Michael McSharry [mailto:mcs101main@xxxxxxx]
<B>Sent:</B> 17 February 2004 16:44<B>To:</B> <A
href="mailto:xAP_developer@xxxxxxx";>xAP_developer@xxxxxxx</A><B>Subject:</B>
Re: [xAP_developer] Audio Control schema changes</FONT></DIV>
<DIV></DIV>
<DIV><FONT face="Arial"><FONT
size="2">It really does not matter to me about the mechanism
of the query. I'll make use of whatever is available from the
provider. I agree that the Now.Playing is a preferred solution
when it becomes available. <FONT
color="#0000ff"><SPAN
class="480085717-17022004"> </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face="Arial"><FONT
size="2"><FONT color="#0000ff"><SPAN
class="480085717-17022004"></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT face="Arial"><FONT
size="2"><FONT color="#0000ff"><SPAN
class="480085717-17022004">It's nearer than it was before
:-) </SPAN><SPAN
class="480085717-17022004"> </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face="Arial"><FONT
size="2"><SPAN
class="480085717-17022004"></SPAN></FONT></FONT> </DIV>
<DIV><FONT face="Arial" size="2">I don't
like the idea of periodic info messages floating all over the network when
there is no receiver actually wanting them. A query based upon a
target's need is generally a more efficient mechanism to induce a message
notification than an internal timer at the source.<SPAN
class="480085717-17022004"><FONT
color="#0000ff"> </FONT></SPAN></FONT></DIV>
<DIV><FONT face="Arial" size="2"><SPAN
class="480085717-17022004"></SPAN></FONT> </DIV>
<DIV><FONT face="Arial" color="#0000ff"
size="2"><SPAN class="480085717-17022004">The
design concept of xAP means that you are not aware what (if
anything) is listening so you do need to provide such information.
A contrast is that when info is needed by several devices
they don't each have to ask for it. Cache systems and controllers
can also monitor passively. Timers are not typically used
to provide this periodic reporting/status - a xAP implementation would by
choice only broadcast new data when an 'event' had occurred
that superceded the validity of the last data
sent - this is not always true as the implementation is under the
developers control of course. Once point to point dependencies get set up
then you drift towards a need to know exactly where things are located and
you get software locks appearing when a service is unavailable.
In practica
lity the volume of traffic certainly on an Ethernet connection is many
orders of magnitude from being significant
anyway</SPAN></FONT></DIV>
<DIV><FONT face="Arial" color="#0000ff"
size="2"><SPAN
class="480085717-17022004"></SPAN></FONT> </DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT size="2"><SPAN
class="480085717-17022004"> </SPAN>
If a target does want periodic updates then a request mechanism could exist
in the schema where the query parameter includes the frequency
of response where the default is once. I am sensitive to
garbage that pollutes the network. As garbage gets old it starts
stinking and then it is a mess to clean up.<SPAN
class="480085717-17022004"><FONT
color="#0000ff"> </FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT size="2"><SPAN
class="480085717-17022004"></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT size="2"><SPAN
class="480085717-17022004"><FONT
color="#0000ff">A rather loaded analogy as all data
is transient - a polling scenario, particularly of the frequency
of MSC Music which I think defaulted to every 2 seconds or so generates
</FONT> <FONT color="#0000ff">a
comparitively large volume of such 'garbage' as far as other receivers are
concerned so I feel event triggered is absolutely the right
approach.</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT color="#0000ff"
size="2"><SPAN
class="480085717-17022004"></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT color="#0000ff"
size="2"><SPAN class="480085717-17022004">The
Slim CLI interface implementation is
very verbose when utilised in an event triggered
mode</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT color="#0000ff"
size="2"><SPAN
class="480085717-17022004"></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT size="+0"><FONT
face="Arial"><FONT color="#0000ff"
size="2"><SPAN
class="480085717-17022004">
Kevin</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV> </DIV></BLOCKQUOTE>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|