[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
BSC and OneWire
------=_NextPart_000_004F_01C4D20C.6013B000
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I have a set of Dallas 1-wire networks running under xap using the OneWire
=
schema I proposed about 6 months ago and am considering BSC, but I have a
d=
ilema with respect to my xapDataCollection node. It captures all messages
=
on the OneWire schema, but I do not want it to capture all BSC messages of
=
which the 1-wire sensor messages would be a subset. I've considered
adding=
a flag as part of the source subaddress field so the transmitter can ident=
ify the sensor value to be recordable. I've also considered adding an
addi=
tional key to the Info and Event BSC message for this purpose. My least
fa=
vorite choice it to put a GUI interface on xapDataCollection where
individu=
al messages can be selected for recording. I really want the
recordability=
knowledge to exist at the source rather than at the target. The easiest s=
olution is to just leave well-enough-alone and not break something that is
=
already working.
Is there a preferred technique to handle this general class of problem
wher=
e the source wants to convey information as part of the message, but the
sc=
hema does not directly support such a capability?
------=_NextPart_000_004F_01C4D20C.6013B000
Content-Type: text/html; charset=ISO-8859-1
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=iso-8859-1">
<META content="MSHTML 6.00.2800.1476" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I have a set of Dallas 1-wire
networks running
under xap using the OneWire schema I proposed about 6 months ago and am
considering BSC, but I have a dilema with respect to my xapDataCollection
node. It captures all messages on the OneWire schema, but I do
not want it
to capture all BSC messages of which the 1-wire sensor messages would be a
subset. I've considered adding a flag as part of the source
subaddress
field so the transmitter can identify the sensor value to be
recordable.
I've also considered adding an additional key to the Info and
Event BSC
message for this purpose. My least favorite choice it to put a
GUI
interface on xapDataCollection where individual messages can be selected
for
recording. I really want the recordability knowledge to exist at
the
source rather than at the target. The easiest solution is to just
leave
well-enough-alone and not break something that is already
working.</FONT></DIV>
<DIV><FONT face=Arial
size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Is there a preferred technique to
handle this
general class of problem where the source wants to convey information as
part of
the message, but the schema does not directly support such a
capability?</FONT></DIV>
<DIV><FONT face=Arial
size=2></FONT> </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=129rq3fae/M=298184.5639630.6699735.3001176/D=groups/S=1705007709:HM/EXP=1101405342/A=2434970/R=0/SIG=11edksnhv/*http://www.netflix.com/Default?mqso=60185402"
alt=""><img src="http://us.a1.yimg.com/us.yimg.com/a/ne/netflix/111704_1104_f_300250a.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.5639630.6699735.3001176/D=groups/S=:HM/A=2434970/rand=275935683"></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>
<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>
<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_004F_01C4D20C.6013B000--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|