[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: BSC spec query
--------------000205080106060805010202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
g8kmh wrote:
>>> Also there's a typo on page 8, para 2 which I think should be
>>> xAPBSC.query and then another para should be added for the
case
>>>
> where
>
>>> an xAPBSC.cmd results in no change of status.
>>>
>>>
>> Can you confirm exactly what/where this is. I read para 2 and I
>>
> think it
>
>> is correct as written (as a response to a xAPBSC.cmd message). I
>>
> agree
>
>> that we could do with clarification on which response to send when
>>
> a
>
>> xAPBSC.cmd is sent that doesn't actually result in a state change.
>>
> It
>
>> should be a xAPBSC.info.
>>
>>
>
> Yep, that's the section. I'd suggest something like:
>
> A xAPBSC.info must be returned by a device supporting BSC whenever a
> xAPBSC.query message
> is received querying the status of that endpoint.
>
> A xAPBSC.info must be returned by a device supporting BSC whenever a
> xAPBSC.cmd message
> is received which results in no change to the state of the device.
>
Will give this some thought tomorrow (too may beers) as we are amending
the text in the xapbsc.event sub section and yet this really relates to
xAPBSC.info's...
We also need to slightly adapt the first one to cater for the situation
where a device is not reporting all its state changes in realtime (eg
for an A/D converter or similar). Perhaps...
A xAPBSC.info must be returned by a device supporting BSC whenever a
xAPBSC.query message is received querying the status of that endpoint and
its current state is unchanged from that last reported . If the state has
changed however then a xAPBSC.event message should be returned instead. A
device should always report it's current state (see NB at the end of this
section)
K
--------------000205080106060805010202
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">
g8kmh wrote:
<blockquote cite="middoa3ac+hei6@xxxxxxx"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Also there's a typo on page 8, para 2 which I
think should be
xAPBSC.query and then another para should be added for the case
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->where
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">an xAPBSC.cmd results in no change of status.
</pre>
</blockquote>
<pre wrap="">Can you confirm exactly what/where this is. I
read para 2 and I
</pre>
</blockquote>
<pre wrap=""><!---->think it
</pre>
<blockquote type="cite">
<pre wrap="">is correct as written (as a response to a
xAPBSC.cmd message). I
</pre>
</blockquote>
<pre wrap=""><!---->agree
</pre>
<blockquote type="cite">
<pre wrap="">that we could do with clarification on which
response to send when
</pre>
</blockquote>
<pre wrap=""><!---->a
</pre>
<blockquote type="cite">
<pre wrap="">xAPBSC.cmd is sent that doesn't actually
result in a state change.
</pre>
</blockquote>
<pre wrap=""><!---->It
</pre>
<blockquote type="cite">
<pre wrap="">should be a xAPBSC.info.
</pre>
</blockquote>
<pre wrap=""><!---->
Yep, that's the section. I'd suggest something like:
A xAPBSC.info must be returned by a device supporting BSC whenever a
xAPBSC.query message
is received querying the status of that endpoint.
A xAPBSC.info must be returned by a device supporting BSC whenever a
xAPBSC.cmd message
is received which results in no change to the state of the device.
</pre>
</blockquote>
<br>
Will give this some thought tomorrow (too may beers) as we are amending
the text in the xapbsc.event sub section and yet this really relates to
xAPBSC.info's...<br>
<br>
We also need to slightly adapt the first one to cater for the situation
where a device is not reporting all its state changes in realtime (eg
for an A/D converter or similar). Perhaps...<br>
<br>
<pre wrap="">A xAPBSC.info must be returned by a device
supporting BSC whenever a xAPBSC.query message is received querying the
status of that endpoint and its current state is unchanged from that last
reported . If the state has changed however then a xAPBSC.event message
should be returned instead. A device should always report it's current
state (see NB at the end of this section)
</pre>
<br>
K<br>
<!-- **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=Filemaker+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=XT_nkUehS9u3WeiIvqWVCQ";>Filemaker
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Sql+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=z-elEO8RXPrD4gH1kbXyQQ";>Sql
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Computer+internet+security&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=NzrSvo0tBwvI1ePKKK_DEg";>Computer
internet security</a></tt>
</td>
</tr>
<tr valign=top>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Web+developer&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=mjd58dX9AWFwX-2eGRXvng";>Web
developer</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Developer+tool&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=Qz1EmmfcCNmAHMEh24Yihg";>Developer
tool</a></tt>
</td>
<td style="width:25%;">
<tt><a href="http://groups.yahoo.com/gads?t=ms&k=Computer+internet+training&w1=Filemaker+developer&w2=Sql+developer&w3=Computer+internet+security&w4=Web+developer&w5=Developer+tool&w6=Computer+internet+training&c=6&s=147&.sig=p-KCJo-Z8iJg3wolqMUR1g";>Computer
internet training</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>
--------------000205080106060805010202--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|