Re: Re: xAP slimserver Connector, Homeseer, HS xAP plugin

[Lehane Kellett <lehane@xxxxxxxxxxxxxxxxxxx>]

--------------060701040405040204070508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

In either case keeping up with the code base is always a problem. On
balance
keeping on the CLI interface is still the way to go, although I
currently only have
one Squeezebox (and two Rio's but that's another story...).

Probably the one piece of source I don't have is the slim connector but
if Stuart
made it available then I could take a look - the downside is that I'd
have to
move to .NET 2.0 as that is my dev environment now and where my personal
copy of xFx has migrated to.

I guess most devices perform their queing independently (or not at all)
which can
lead to some oddities. An xAP queue application would resolve those and
could reduce
the coding effort in the final clients too.

Lehane


Kevin Hawkins wrote:
>
> --- In xap_automation@xxxxxxx
> <mailto:xap_automation%40yahoogroups.com>,
Lehane Kellett <lehane@...>
> wrote:
> >
> > Yes,
> > I've seen the same.
> >
> > It makes me wonder whether native xAP support in the Slimserver
is the
> > way forward (as xPL). I did add some code to the xPL module for
my own
> > use a while back, when I was using xPL, for some alarm and power
events
> > - I didn't submit them to the nightlies though.
>
> I did the same - I have an adaption of the xPL perl code that talks
> xAP instead but the reality is that the xPL code offers very little
> feature support for SlimServer . The xAP connector offers far more
> including the most useful (multiplayer, prioritised) display queing
> which I find invaluable. Also SlimDevices would prefer the xPL code
> (or should I say any future similar versions eg xAP) implemented as a
> plugin and not as core code
>
> I am in two minds about the integrated vs standalone/CLI
advantages....
>
> Implementing a plugin requires a very good understanding of the
> SlimServer code base and that is a constantly moving target with daily
> updates - I have seen more than a few such authors give up in the end
> and maintain compatability only with certain older versions. It means
> coding some quite involved stuff in Perl in an open source project and
> also places more processing onto SlimServer which struggles at the
> moment to provide adequate performance.
>
> The CLI has been honed quite a bit recently and offers very powerful
> chunk based library searches - really to enhance integration with
> external controllers eg AMX and Crestron, this makes it well suited to
> the xAP media schema. Also it's now of a maturity that you can moan at
> the developers should it break or change which eases maintainance.
> However this makes setup more complex, introduces platform dependence
> (in the xAP connector code)and also means another layer in the
> implementation.
>
> Overall I'm slightly siding on the CLI as the most viable approach,
> particularly because of the display queue management and some exiting
> code to work from. I wonder if Stuart might be able to provide the
> source code for the SlimServer conduit - would you (or anyone)
> familiar with C# be able to give this a once over to see if we can
> firstly fix the reported issue with stability and response, and
> secondly I would have a look at the CLI issues. I can adapt the CLI
> code without too much problem although as I dont know C# I might need
> some help in the syntax area.
>
> At one time I also was talking to Stuart about breaking out the queue
> management portion into a standalone xAP network function. This type
> of intelligent multi destination, multi priority , timed queue has
> many applications in HA and could be a useful standard xAP message
> queue feature , not just limited to display messages ... if that could
> be done then the internal/external Slimserver conduit debate would be
> different again.
>
> Kevin
>
> >
>
>
>
------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.9.9/382 - Release Date:
04/07/2006
>


--------------060701040405040204070508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">


In either case keeping up with the code base is always a problem. On
balance<br>
keeping on the CLI interface is still the way to go, although I
currently only have<br>
one Squeezebox (and two Rio's but that's another story...).<br>
<br>
Probably the one piece of source I don't have is the slim connector but
if Stuart<br>
made it available then I could take a look - the downside is that I'd
have to<br>
move to .NET 2.0 as that is my dev environment now and where my
personal<br>
copy of xFx has migrated to.<br>
<br>
I guess most devices perform their queing independently (or not at all)
which can<br>
lead to some oddities. An xAP queue application would resolve those and
could reduce<br>
the coding effort in the final clients too.<br>
<br>
Lehane<br>
<br>
<br>
Kevin Hawkins wrote:
<blockquote cite="mide8nvak+h377@xxxxxxx"
type="cite"><!-- Network content -->

<div id="ygrp-text">
<p>--- In <a href="mailto:xap_automation%40yahoogroups.com";>xap_automation@<wbr>yahoogroups.<wbr>com</a>,
Lehane Kellett <a class="moz-txt-link-rfc2396E" href="mailto:lehane@...";>&lt;lehane@...&gt;</a>
wrote:<br>
&gt;<br>
&gt; Yes,<br>
&gt; I've seen the same.<br>
&gt; <br>
&gt; It makes me wonder whether native xAP support in the Slimserver is
the <br>
&gt; way forward (as xPL). I did add some code to the xPL module for my
own <br>
&gt; use a while back, when I was using xPL, for some alarm and power
events <br>
&gt; - I didn't submit them to the nightlies though.<br>
<br>
I did the same - I have an adaption of the xPL perl code that
talks<br>
xAP instead but the reality is that the xPL code offers very
little<br>
feature support for SlimServer . The xAP connector offers far
more<br>
including the most useful (multiplayer, prioritised) display
queing<br>
which I find invaluable. Also SlimDevices would prefer the xPL
code<br>
(or should I say any future similar versions eg xAP) implemented as
a<br>
plugin and not as core code <br>
<br>
I am in two minds about the integrated vs standalone/CLI
advantages..<wbr>..<br>
<br>
Implementing a plugin requires a very good understanding of the<br>
SlimServer code base and that is a constantly moving target with
daily<br>
updates - I have seen more than a few such authors give up in the
end<br>
and maintain compatability only with certain older versions. It
means<br>
coding some quite involved stuff in Perl in an open source project
and<br>
also places more processing onto SlimServer which struggles at
the<br>
moment to provide adequate performance. <br>
<br>
The CLI has been honed quite a bit recently and offers very
powerful<br>
chunk based library searches - really to enhance integration with<br>
external controllers eg AMX and Crestron, this makes it well suited
to<br>
the xAP media schema. Also it's now of a maturity that you can moan
at<br>
the developers should it break or change which eases
maintainance.<br>
However this makes setup more complex, introduces platform
dependence<br>
(in the xAP connector code)and also means another layer in the<br>
implementation. <br>
<br>
Overall I'm slightly siding on the CLI as the most viable
approach,<br>
particularly because of the display queue management and some
exiting<br>
code to work from. I wonder if Stuart might be able to provide
the<br>
source code for the SlimServer conduit - would you (or anyone)<br>
familiar with C# be able to give this a once over to see if we
can<br>
firstly fix the reported issue with stability and response, and<br>
secondly I would have a look at the CLI issues. I can adapt the
CLI<br>
code without too much problem although as I dont know C# I might
need<br>
some help in the syntax area.<br>
<br>
At one time I also was talking to Stuart about breaking out the
queue<br>
management portion into a standalone xAP network function. This
type<br>
of intelligent multi destination, multi priority , timed queue
has<br>
many applications in HA and could be a useful standard xAP
message<br>
queue feature , not just limited to display messages ... if that
could<br>
be done then the internal/external Slimserver conduit debate would
be<br>
different again.<br>
<br>
Kevin<br>
<br>
&gt; <br>
<br>
</p>
</div>

<!--End group email -->
<pre wrap="">
<hr size="4" width="90%">
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.9/382 - Release Date: 04/07/2006
</pre>
</blockquote>
<br>

<span width="1" style="color:
white;"/>__._,_.___</span>


<!-- **begin egp html banner** -->

<img src="http://geo.yahoo.com/serv?s=97476590&amp;grpId=9674343&amp;grpspId=1600007709&amp;msgId=2814&amp;stime=1152353450";
width="1" height="1"> <br>

<!-- **end egp html banner** -->


<!-- **begin egp html banner** -->

<br><br>
<div style="width:500px; text-align:right; margin-bottom:1px;
color:#909090;">
<tt>SPONSORED LINKS</tt>
</div>
<table bgcolor=#e0ecee cellspacing="13"
cellpadding="0" width=500px>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjbnAwYjViBF9TAzk3NDc2NTkwBF9wAzEEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18ik8abg5/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Workflow%2bautomation%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=y3Kx4mJhI61V0cvcP76Q-g";>Workflow
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjYTMzcDVlBF9TAzk3NDc2NTkwBF9wAzIEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18jqfc75j/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Automation%2bequipment%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=a1PsPQf6m4nTJ4kTniDcWw";>Automation
equipment</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjaWhlbjVhBF9TAzk3NDc2NTkwBF9wAzMEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18k92fi9s/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Industrial%2bautomation%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=a6YXofYCAugLROGBil84Ug";>Industrial
automation</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjOG9qY2I3BF9TAzk3NDc2NTkwBF9wAzQEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18e4n3e5b/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Test%2bautomation%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=yoUYYFsDWq7xZXeu7WMPJA";>Test
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjZGYzMDgwBF9TAzk3NDc2NTkwBF9wAzUEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18hutjv2u/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Factory%2bautomation%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=-LZRq1wLfZ87FijSLZQCkA";>Factory
automation</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://us.lrd.yahoo.com/_ylc=X3oDMTJjZ2ttNjJxBF9TAzk3NDc2NTkwBF9wAzYEZ3JwSWQDOTY3NDM0MwRncnBzcElkAzE2MDAwMDc3MDkEc2VjA3NsbW9kBHN0aW1lAzExNTIzNTM0NTA-;_ylg=1/SIG=18gnaqms5/**http%3a//groups.yahoo.com/gads%3ft=ms%26k=Automation%2bsystem%26w1=Workflow%2bautomation%26w2=Automation%2bequipment%26w3=Industrial%2bautomation%26w4=Test%2bautomation%26w5=Factory%2bautomation%26w6=Automation%2bsystem%26c=6%26s=146%26g=0%26.sig=0LEkL9LxR9JVf3U2mXjWhQ";>Automation
system</a></tt>
</td>
</tr>
</tr>
</table>

<!-- **end egp html banner** -->



<!-- **begin egp html banner** -->

<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
<tt>YAHOO! GROUPS LINKS</tt>
</div>
<br>
<ul>
<tt><li type=square>&nbsp;Visit your group "<a
href="http://groups.yahoo.com/group/xap_automation";>xap_automation</a>"
on the web.<br>&nbsp;</tt>
<tt><li type=square>&nbsp;To unsubscribe from this group,
send an email to:<br>&nbsp;<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>xap_automation-unsubscribe@xxxxxxx</a><br>&nbsp;</tt>
<tt><li type=square>&nbsp;Your use of Yahoo! Groups is
subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.</tt>
</ul>
<br>
<div style="text-align:center; color:#909090;
width:500px;">
<hr style="border-bottom:1px; width:500px;
text-align:left;">
</div>
</br>

<!-- **end egp html banner** -->


<span  style="color: white;"/>__,_._,___</span>
</body>
</html>

--------------060701040405040204070508--