[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Xap and serial
------=_Part_20574_1653423.1171811724732
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Guys,
Sorry to wade in to the conversation late. As Kevin hints, this situation
was anticipated when the original xAP spec was written, and the intention
was that the bridge should filter between networks using the source, target
and class elements of the header as criteria.
In my own implementation, I have also re-written packets at the bridge,
discarding stuff that I knew was not of interest on the slower network.
The implementation of flow control in a multi-sender, multi-receiver
environment is fraught with difficulties, and also has the potential to
impact the responsiveness of devices. Flow controlling a device which
relays
light-switching requests, for example would be highly undesirable. You can
work around these problems, but doing so is going to significantly increase
the complexity of xAP and would also raise the bar in terms of processing
and memory requirements for network members.
Patrick
------=_Part_20574_1653423.1171811724732
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html><body>
Hi Guys,<br>
Sorry to wade in to the conversation late. As Kevin hints, this
situation was anticipated when the original xAP spec was written, and
the intention was that the bridge should filter between networks using
the source, target and class elements of the header as criteria.<br>
<br>
In my own implementation, I have also re-written packets at the bridge,
discarding stuff that I knew was not of interest on the slower
network.<br>
<br>
The implementation of flow control in a multi-sender, multi-receiver
environment is fraught with difficulties, and also has the potential to
impact the responsiveness of devices. Flow controlling a device which
relays light-switching requests, for example would be highly
undesirable. You can work around these problems, but doing so is going
to significantly increase the complexity of xAP and would also raise
the bar in terms of processing and memory requirements for network
members.<br>
<br>
Patrick<br>
<br>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=3497/stime=1171811821";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmMHZnbzM2BF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzExNzE4MTE4MjE-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkM2Uyb2xuBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMTcxODExODIx";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</body></html>
------=_Part_20574_1653423.1171811724732--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|