[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xAP EOM identifier in xAP v1.3
--001485e8cb1fa070fd047379aee5
Content-Type: text/plain; charset=ISO-8859-1
The original xap spec provides extensions for framing a message over async
serial which also delimit the start of the message - you don't need this
'hack' if you follow the original spec for non-UDP transports.
Patrick
2009/9/13 Kevin Hawkins <yahoogroupskh@xxxxxxx>
> We have been asked on several occasions how to detect the end of a
> xAP messager as there is no unique EOM character. Typically in any
> reasonable sized packet structured transport eg UDP then the packet
> provides such an indication but on systems with small packets or non
eg
> asynchronous serial this is not useable.
>
> In discussing this with the specification team we must consider
> backwards compatability and so we do not wish to alter the
specification
> to include a unique EOM character. What we do propose however is that
> xAP v1.3 will specify that all messages should end with two
consecutive
> chr(10)'s immediately after the closing '}'
>
> ie ..... 7D 0A 0A
>
> Some apps, even v1.2 ones, already do this. We don't believe this
> will cause any backwards compatibility issues and it will always be
> unique within a xAP message.
>
> So, in developing xAP v1.3 apps could you therefore append two 0A's
> at the end of your messages , and of course handle incoming messages
> containing such.
>
> K
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
--001485e8cb1fa070fd047379aee5
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** -->
The original xap spec provides extensions for framing a message over async
=
serial which also delimit the start of the message - you don't need
thi=
s 'hack' if you follow the original spec for non-UDP
transports.<br=
>
<br>Patrick<br><br><div
class=3D"gmail_quote">2009/9/13 Kevin Hawkins <span=
dir=3D"ltr"><<a href=3D"mailto:yahoogroupskh@xxxxxxx";>yahoogroup=
skh@xxxxxxx</a>></span><br><blockquote
class=3D"gmail_quote" styl=
e=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt
0.8ex; =
padding-left: 1ex;">
=A0 We have been asked on several occasions how to detect the end of
a<br>
xAP messager as there is no unique EOM character. =A0Typically in
any<br>
reasonable sized packet structured transport eg UDP then the
packet<br>
provides such an indication but on systems with small packets or non
eg<br>
asynchronous serial this is not useable.<br>
<br>
=A0 In discussing this with the specification team we must
consider<br>
backwards compatability and so we do not wish to alter the
specification<br=
>
to include a unique EOM character. =A0What we do propose however is
that<br=
>
xAP v1.3 will specify that all messages should end with two
consecutive<br>
chr(10)'s immediately after the closing
'}'<br>
<br>
ie =A0..... 7D 0A 0A<br>
<br>
=A0Some apps, even v1.2 ones, =A0already do this. =A0We don't
believe =
this<br>
will cause any backwards compatibility issues and it will always
be<br>
unique within a xAP message.<br>
<br>
=A0So, in developing xAP v1.3 apps could you therefore append =A0two
0A=
9;s<br>
at the end of your messages , and of course handle incoming
messages<br>
containing such.<br>
<br>
=A0 K<br>
<br>
<br>
------------------------------------<br>
<br>
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|