The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Total Telematics board




------=_NextPart_000_0028_01C52FEC.DD11DD50
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

A flurry of messages recently concerning the Total Telematics single board
computer on ukha_d.

Looks like an ideal xAP host - but I note that it uses the same processor
as
the WebBrick so does that mean it has the same UDP issues that preculde it
from xAP on UDP? Are the WebBrick's UDP problems hardware dependent or to
do
with the IP stack? Not sure if the stack is the same between the two. Mark,
you maybe the most qualified to comment (but please keep your views on cars
out of this thread!)

Edward

------=_NextPart_000_0028_01C52FEC.DD11DD50
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html;
charset=us-ascii">
<META content="MSHTML 6.00.2900.2604"
name=GENERATOR></HEAD>
<BODY>


<DIV><SPAN class=343020621-23032005><FONT face=Arial
color=#0000ff size=2>A
flurry of messages recently concerning the Total Telematics single board
computer on ukha_d.</FONT></SPAN></DIV>
<DIV><SPAN class=343020621-23032005><FONT face=Arial
color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=343020621-23032005><FONT face=Arial
color=#0000ff size=2>Looks
like an ideal xAP host - but I note that it uses the same processor as the
WebBrick so does that mean it has the same UDP issues that preculde it from
xAP
on UDP? Are the WebBrick's UDP problems hardware dependent or to do with
the IP
stack? Not sure if the stack is the same between the two. Mark, you maybe
the
most qualified to comment (but please keep your views on cars out of this
thread!)</FONT></SPAN></DIV>
<DIV><SPAN class=343020621-23032005><FONT face=Arial
color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=343020621-23032005><FONT face=Arial
color=#0000ff
size=2>Edward</FONT></SPAN></DIV>

<br>

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

<table border=0 cellspacing=0 cellpadding=2>
<tr bgcolor=#FFFFCC>
<td align=center><font size="-1"
color=#003399><b>Yahoo! Groups
Sponsor</b></font></td>
</tr>
<tr bgcolor=#FFFFFF>
<td align=center width=470><table border=0 cellpadding=0
cellspacing=0> <tr> <td align=center><font face=arial
size=-2>ADVERTISEMENT</font><br><a href="http://us.ard.yahoo.com/SIG=129fqbvse/M=298184.6191685.7192823.3001176/D=groups/S=1705007709:HM/EXP=1111698698/A=2593423/R=0/SIG=11el9gslf/*http://www.netflix.com/Default?mqso=60190075";
alt=""><img src="http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/22305_0205_016_b_300250_a.gif";
alt="click here" width="300" height="250"
border="0"></a></td></tr></table>
</td>
</tr>
<tr><td><img alt="" width=1 height=1 src="http://us.adserver.yahoo.com/l?M=298184.6191685.7192823.3001176/D=groups/S=:HM/A=2593423/rand=515721791";></td></tr>
</table>

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



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

<br>
<tt><hr width="500">
<b>Yahoo! Groups Links</b><br>
<ul>
<li>To visit your group on the web, go to:<br><a
href="http://groups.yahoo.com/group/xAP_developer/";>http://groups.yahoo.com/group/xAP_developer/</a><br>&nbsp;
<li>To unsubscribe from this group, send an email to:<br><a
href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>xAP_developer-unsubscribe@xxxxxxx</a><br>&nbsp;
<li>Your use of Yahoo! Groups is subject to the <a href="http://docs.yahoo.com/info/terms/";>Yahoo!
Terms of Service</a>.
</ul>
</tt>
</br>

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


</BODY></HTML>

------=_NextPart_000_0028_01C52FEC.DD11DD50--




xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.