xAP_developer at Yahoo! Groups

Re: xAP EOM identifier in xAP v1.3

Patrick Lidstone — Fri, 18 Sep 2009 07:50:40 GMT

2009/9/17 Edward Pearson ... Your wifi bandwidth gets eaten up o(n) for number of wifi endpoints, the bw is contended for

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 22:18:55 GMT

Fantastic stuff! Have a Greeaat weekend - congratulations! From: xAP_developer@yahoogroups.com [mailto:xAP_developer@yahoogroups.com] On Behalf Of Neil

Re: xAP EOM identifier in xAP v1.3

Neil Wrightson — Thu, 17 Sep 2009 21:48:07 GMT

Hi, I can't get into this to much at the moment, I'm supposed to be getting ready for a dirty (oops romantic) weekend with my wife. Today is our 27th wedding

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 16:20:34 GMT

... scale very well... Yes it would forward all traffic. How does that create a scalability problem Patrick? Obviously there's more traffic, now o(n) rather

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 14:56:30 GMT

How big are the buffers on your device? What is it BTW? I'm sure we're all curious now (or have I missed/forgotten an earlier post)? From:

Re: xAP EOM identifier in xAP v1.3

Neil Wrightson — Thu, 17 Sep 2009 13:58:26 GMT

That's why I had length=nnnn (4 digit field length, padded 0's as per my header example) Actually, I was thinking in HEX not decimal so nnnn hex = 65535 not

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 12:58:41 GMT

... "tody" - is that a Yorkshire word? Assuming it's a typo, what did you mean. I'm probably having a dense moment but I don't know what you meant. Actually

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 12:46:50 GMT

The trouble is that to generate such a message you need to know how long it's going to be before you generate it and then inserting the length field could

Re: xAP EOM identifier in xAP v1.3

Kevin Hawkins — Thu, 17 Sep 2009 12:46:45 GMT

Nothing should break by adding any parameter within a header but of course you would need every app to support it and no existing ones do (although it could be

Re: xAP EOM identifier in xAP v1.3

Neil Wrightson — Thu, 17 Sep 2009 12:35:41 GMT

Just out of curiosity, how many things would break if the xAP header had a message length? I.e. add a length=nnnn line. xap-header { v=12 hop=1 uid=FF123400

Re: xAP v1.3

Neil Wrightson — Thu, 17 Sep 2009 12:35:19 GMT

Hi Kevin, Thanks for responding. To me, things that would have watchdog capability, would generally be controlled by one governing box PC i.e. MisterHouse

Re: xAP EOM identifier in xAP v1.3

Edward Pearson — Thu, 17 Sep 2009 12:20:46 GMT

Sigh. You misread. I said (or at least intended to say) enforcing the transport wrapper on >UDP< would break everything (obviously). My experience of it on TCP

Re: xAP v1.3

Kevin Hawkins — Thu, 17 Sep 2009 12:08:28 GMT

Hi Neil, Glad it's all progressing. I think this sort of issue does need a solution so glad you're tackling it. A couple of thoughts. I would try and avoid

xAP v1.3

Neil Wrightson — Thu, 17 Sep 2009 11:37:05 GMT

Hi, I'm still in the progress of creating my first BSC device and I'm looking at adding a few extensions to the common BSC schema. From an output end point

Re: xAP EOM identifier in xAP v1.3

Patrick Lidstone — Thu, 17 Sep 2009 11:32:08 GMT

No arguments here - I just haven't got round to it! Patrick 2009/9/17 Kevin Hawkins