[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Audio Control schema changes
- Subject: RE: Audio Control schema changes
- From: Edward Pearson
- Date: Mon, 16 Feb 2004 22:44:00 +0000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<TITLE>Message</TITLE>
<DIV><SPAN class="372062522-16022004"><FONT
face="Arial" color="#0000ff" size="2">I'm
dubious about the usefulness of such fine-grained queries. For example, I
can't imagine what kind of application would be in need of
information on the artist of a particular track in the playlist but is not
interested in the title of the track. Or just the Genre. Do you have a
real-world need for this granularity?</FONT></SPAN></DIV>
<DIV><SPAN class="372062522-16022004"><FONT
face="Arial" color="#0000ff"
size="2"></FONT></SPAN> </DIV>
<DIV><SPAN class="372062522-16022004"><FONT
face="Arial" color="#0000ff" size="2">If
the main reason is bandwidth concerns then I'd counter that such a scheme
would increase the amount of packets being sent (and thus bandwidth used)
considerably. On an ethernet network, even with something very 'chatty'
such as xAP-News the bandwidth used is barely mesurable. For serial
networks I understand that the general thinking is now that the
ethernet-serial xAP bridge will have to have pretty tight filtering setup
to ensure the serial side only carries information relevant to the devices
on that segment. The difference in bandwidth between these two most common
transports is many orders of magnitude so they have to be treated quite
differently.</FONT></SPAN></DIV>
<DIV><SPAN class="372062522-16022004"><FONT
face="Arial" color="#0000ff"
size="2"></FONT></SPAN> </DIV>
<DIV><SPAN class="372062522-16022004"><FONT
face="Arial" color="#0000ff" size="2">I'm
wary (when defining any software interface not just xAP) of getting into
theoretical discussions that add unneccesary complexity without any
real-world need. The spirit of xAP is very much one of simplicity;
my suggested changes to the audio schema were aimed at triming down the
number of variations of messages and getting away from the earlier
fine-grained query scheme.</FONT></SPAN></DIV>
<BLOCKQUOTE dir="ltr">
<DIV></DIV>
<DIV class="OutlookMessageHeader" lang="en-us"
dir="ltr" align="left"><FONT
face="Tahoma" size="2">-----Original
Message-----<B>From:</B> Michael McSharry [mailto:mcs101main@xxxxxxx]
<B>Sent:</B> 14 February 2004 18:45<B>To:</B>
xAP_developer@xxxxxxx<B>Subject:</B> Re: [xAP_developer] Audio
Control schema changes</FONT></DIV>
<DIV><FONT face="Arial" size="2">I
generally agree with information returned in block format, but at the same
time consideration should be given to low bandwith interfaces as well as
the general proliferation where the "state" of all providers is
clogging up the network. When a query is made it should be
possible to query either a particular key or a group. This will
allow the optimum level of traffic as determined by the unit that is in
need of the information.</FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV><FONT face="Arial" size="2">Using the
example</FONT></DIV>
<DIV><FONT face="Arial"
size="2"></FONT> </DIV>
<DIV><FONT face="Courier
New">[Request]Class=xAP-Audio.QueryPlaylist.Query{
Query=[Track List Title Artist Album Path Duration Index Tracks
Genre] Index="index in
playlist"}[Response - where
Query=Track]Class=xAP-Audio.Playlist.InfoTrack.Info{
Title="title"
Artist="artist"
Album="album" Path="path to
current track" Duration="title
duration" Index="playlist
index" Tracks="number of tracks in
the current playlist"
Genre="genre"}</FONT></DIV>
<DIV><FONT face="Courier
New"></FONT> </DIV>
<DIV><FONT face="Courier New">[Response - where
Query=Artist]Class=xAP-Audio.Playlist.InfoArtist.Info{
Artist="artist"}</FONT></DIV>
<DIV></DIV>
<BLOCKQUOTE>
<DIV><SPAN class="372062522-16022004"><FONT
color="#0000ff"> [originals
truncated] </FONT></SPAN><!-- **end egp html
banner** --></DIV></BLOCKQUOTE></BLOCKQUOTE>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|