[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
bsc questions
- Subject: bsc questions
- From: "Ian Davidson" <ian@xxxxxxxxxxxxxxxx>
- Date: Thu, 11 May 2006 18:36:02 +0100
------_=_NextPart_001_01C67521.5FBCD6BE
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hello
=20
It's my first email to the developers group but I'm struggling to get to
grips with some aspects of xAP. I have looked back through the archives
but still can't quite get to grips with some of the concepts.
=20
If I have understood things correctly then the BSC part was aimed at
lower spec'd devices to be able to utilise xAP.
=20
My biggest problem is fully understanding the UID part. Within the xAP
header the UID identifies the source. For an ouput device to use only
the UID for identification it would mean it could only ever respond to
messages from one device or possibly a number of known devices. Because
the device has used the UID to identify rather than the source or target
then this would also rule out the use of wildcards.
=20
However if the UID was used for a target address then any device could
target the new device. The device would only need to look for and
identify the target UID to know the message is aimed at itself. Again
wildcarding as currently defined would not be possible. Even though a
target UID had been specified it would not be exclusive and there would
be nothing to stop other devices receiving the information as is current
with the broadcast nature of xAP.
=20
At the moment I can not understand how a low end device could be capable
of receiving and decoding a BSC message. To start with both the source
and target can be 128 bytes in length added to this the fact that
multiple endpoints can be targeted in a single message the length could
easily be more than could be available in some devices.=20
=20
Rather than rabbit on at this stage can anyone explain if I have
misunderstood the BSC specification and what would be the easiest way to
implement a device using a small micro but with a number of input and
outputs attached to the device.
=20
Thanks
=20
Ian D=20
=20
=20
------_=_NextPart_001_01C67521.5FBCD6BE
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<html xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered
medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>Hello<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>It’s my first email
to the developers group but I’m struggling to get to grips with
some
aspects of xAP. I have looked back through the archives but still
can’t
quite get to grips with some of the
concepts.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>If
I have understood
things correctly then the BSC part was aimed at lower spec’d
devices to
be able to utilise
xAP.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>My
biggest problem is
fully understanding the UID part. Within the xAP header the UID identifies
the
source. For an ouput device to use only the UID for identification it would
mean it could only ever respond to messages from one device or possibly a
number of known devices. Because the device has used the UID to identify
rather
than the source or target then this would also rule out the use of
wildcards.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>However if the UID was
used for a target address then any device could target the new device. The
device would only need to look for and identify the target UID to know the
message is aimed at itself. Again wildcarding as currently defined would
not be
possible. Even though a target UID had been specified it would not be
exclusive
and there would be nothing to stop other devices receiving the information
as
is current with the broadcast nature of
xAP.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>At
the moment I can not
understand how a low end device could be capable of receiving and decoding
a
BSC message. To start with both the source and target can be 128 bytes in
length added to this the fact that multiple endpoints can be targeted in a
single message the length could easily be more than could be available in
some devices.
<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>Rather than rabbit on at
this stage can anyone explain if I have misunderstood the BSC specification
and
what would be the easiest way to implement a device using a small micro but
with a number of input and outputs attached to the
device.<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>Thanks<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'>Ian D
<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-align:justify'><font size=3
face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span
style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
<!-- **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://groups.yahoo.com/gads?t=ms&k=Palm+developer&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=s-VhzdIgQqxUdEajDGtCdQ";>Palm
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Filemaker+developer&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=lGgnefWZwGisM8FwbeG8Wg";>Filemaker
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Sql+developer&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=RCEEysgM658XhXL6fkmVHA";>Sql
developer</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Computer+internet+security&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=bIm18F_2jJUWqlxWaPuKKA";>Computer
internet security</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Web+developer&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=rL25Ohn9r_NpW8Pscbl4kg";>Web
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Developer+tool&w1=Palm+developer&w2=Filemaker+developer&w3=Sql+developer&w4=Computer+internet+security&w5=Web+developer&w6=Developer+tool&c=6&s=135&.sig=ps2RfkQzNqD_ZJvU3Sakhw";>Developer
tool</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> Visit your group "<a
href="http://groups.yahoo.com/group/xAP_developer";>xAP_developer</a>"
on the web.<br> </tt>
<tt><li type=square> 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> </tt>
<tt><li type=square> 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** -->
</body>
</html>
------_=_NextPart_001_01C67521.5FBCD6BE--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|