[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP EOM identifier in xAP v1.3
--00c09ffb547852a4c10473b06ec4
Content-Type: text/plain; charset=ISO-8859-1
2009/9/16 Kevin Hawkins <yahoogroupskh@xxxxxxx>
> Patrick Lidstone wrote:
> >
> >
> > I don't think hubs currently send heartbeats? If they do, it's
not
> > explicit in the spec. (Mine doesn't). We also need a mechanism to
> > differentiate between multiple hubs (since most people will
generally
> > run at least one hub per vm).
> All the hubs I use (xFX) send heartbeats and so obviously have a
unique
> name/port/ip identifier.
But how does a client device with no user interface or minimal user
interface get configured? I believe the client should be able to enquire as
to where it is supposed to connect - perhaps a tcp capable hub can respond
to the initial heartbeat originating from a tcp-capable client at start up
with a 'you can connect here' message (which is configured in the hub and
based on UUID). This potentially supports fault tolerance seamlessly
(multiple hubs can be configured to serve the same tcp clients), and it
also
resolves the start up time issues if a client has to wait for heartbeat
from
one or more hubs.
> I thought all xAP app's should send heartbeats.
> >
> > Is a TCP hub going to relay all traffic to all TCP endpoints?
That
> > won't scale very well... but it's also not clear how the
filtering
> > etc. will work. Administering filters manually works fine for the
odd
> > serial segment, but it's not going to be viable for a large
number of
> > endpoints.
> There's an existing application called xServer (by mi4) that was
created
> for internet routing of xAP messages. It supports authentication of
> clients and within the app you can setup device filters and the
> allowable directions of traffic. It supports a couple of different
> message formats depending on the client type connection.
>
> I expanded this to become 'iServer' which supports some extra client
> types (iPhone and C-Bus touch screens) and also added some inbuilt BSC
> schema intelligence. This was used to just transfer state change info
> to dumber clients ie the client wasn't parsing xAP. More
significantly
> I added a client protocol that allows the client to add/remove xAP
> device or schema filters on the fly. So a client that is specifically
> interested in specific devices or schema can create those filters at
> connect. The filters support wildcards too. Now a hub version maybe
> should, or shouldn't support such features but it is an option..
>
>
Dynamic filter creation sounds like just the ticket...
Patrick
--00c09ffb547852a4c10473b06ec4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<head>
<style type=3D"text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title=20
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;=20
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html><head>
<style type=3D"text/css">
<!--
#ygrp-mkp{
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 14px 0px;
padding: 0px 14px;
}
#ygrp-mkp hr{
border: 1px solid #d8d8d8;
}
#ygrp-mkp #hd{
color: #628c2a;
font-size: 85%;
font-weight: bold;
line-height: 122%;
margin: 10px 0px;
}
#ygrp-mkp #ads{
margin-bottom: 10px;
}
#ygrp-mkp .ad{
padding: 0 0;
}
#ygrp-mkp .ad a{
color: #0000ff;
text-decoration: none;
}
-->
</style>
</head>
<body>
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<br><br><div class=3D"gmail_quote">2009/9/16
Kevin Hawkins <span dir=3D"ltr=
"><<a href=3D"mailto:yahoogroupskh@xxxxxxx";>yahoogroupskh@googlem=
ail.com</a>></span><br><blockquote
class=3D"gmail_quote" style=3D"border=
-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex;
padding-lef=
t: 1ex;">
<div class=3D"im">Patrick Lidstone wrote:<br>
><br>
><br>
> I don't think hubs currently send heartbeats? If they do,
it's=
not<br>
> explicit in the spec. (Mine doesn't). We also need a
mechanism to<=
br>
> differentiate between multiple hubs (since most people will
generally<=
br>
> run at least one hub per vm).<br>
</div>All the hubs I use (xFX) send heartbeats and so obviously have
a uniq=
ue<br>
name/port/ip identifier. =A0</blockquote><div><br>But how
does a client dev=
ice with no user interface or minimal user interface get configured? I
beli=
eve the client should be able to enquire as to where it is supposed to
conn=
ect - perhaps a tcp capable hub can respond to the initial heartbeat
origin=
ating from a tcp-capable client at start up with a 'you can connect
her=
e' message (which is configured in the hub and based on UUID). This
pot=
entially supports fault tolerance seamlessly (multiple hubs can be
configur=
ed to serve the same tcp clients), and it also resolves the start up time
i=
ssues if a client has to wait for heartbeat from one or more
hubs.<br>
<br>> I thought all xAP app's should send
heartbeats.<br>
</div><blockquote class=3D"gmail_quote"
style=3D"border-left: 1px solid rgb=
(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;"><div class=
=3D"im">><br>
> Is a TCP hub going to relay all traffic to all TCP endpoints?
That<br>
> won't scale very well... but it's also not clear
how the filte=
ring<br>
> etc. will work. Administering filters manually works fine for the
odd<=
br>
> serial segment, but it's not going to be viable for a
large number=
of<br>
> endpoints.<br>
</div>There's an existing application called xServer (by mi4)
that was =
created<br>
for internet routing of xAP messages. It supports authentication
of<br>
clients and within the app you can setup device filters and the<br>
allowable directions of traffic. It supports a couple of
different<br>
message formats depending on the client type connection.<br>
<br>
I expanded this to become 'iServer' which supports some
extra clien=
t<br>
types (iPhone and C-Bus touch screens) and also added some inbuilt
BSC<br>
schema intelligence. =A0This was used to just transfer state change
info<br=
>
to dumber clients ie the client wasn't parsing xAP. =A0 More
significan=
tly<br>
I added a client protocol that allows the client to add/remove
xAP<br>
device or schema filters on the fly. =A0So a client that is
specifically<br=
>
interested in specific devices or schema can create those filters
at<br>
connect. The filters support wildcards too. =A0 =A0Now a hub version
maybe<=
br>
should, or shouldn't support such features but it is an
option..<br>
<br></blockquote><div><br>Dynamic filter creation
sounds like just the tick=
et... <br><br>Patrick<br></div></div>
<!-- **begin egp html banner** -->
<br>
=20=20=20=20
=20=20=20=20
<br>
<!-- **end egp html banner** -->
<div width=3D"1" style=3D"color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src=3D"http://geo.yahoo.com/serv?s=3D97476590/grpId=3D9629476/grpspI=
d=3D1705007709/msgId=3D2002/stime=3D1253101525" width=3D"1"
height=3D"1"> <=
br>
<!-- **end egp html banner** -->
=20=20
<!-- **begin egp html banner** -->
<br>
<div style=3D"font-family: verdana; font-size: 77%; border-top: 1px
s=
olid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href=3D"http://groups.yahoo.com/group/xAP_developer/join;_ylc=3DX3=
oDMTJmZjA2MGcwBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5B=
HNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNTMxMDE1MjU-">Change settings
via the We=
b</a> (Yahoo! ID required) <br>
Change settings via email: <a href=3D"mailto:xAP_developer-digest@yah=
oogroups.com?subject=3DEmail Delivery: Digest">Switch delivery to
Daily Dig=
est</a> <a href =3D "mailto:xAP_developer-fullfeatured@xxxxxxx?su=
bject=3DChange Delivery Format: Fully Featured">Switch to Fully
Featured</a=
> <br>
<a href=3D"http://groups.yahoo.com/group/xAP_developer;_ylc=3DX3=
oDMTJkbGJ2dXBlBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5B=
HNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjUzMTAxNTI1">
Visit Your Group=20
</a>
<a href=3D"http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href=3D"mailto:xAP_developer-unsubscribe@xxxxxxx?subject=
=3DUnsubscribe">
Unsubscribe=20
</a>=20
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style=3D"color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--00c09ffb547852a4c10473b06ec4--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|