[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Re: Proposals for xAP TSC
--------------050301010003060204030408
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
One other aspect about storing endpoint data that I implemented in my
embedded devices. Where a string value (char array) is involved rather
than using fixed length fields and hence having fixed size structures -
half of which might be empty I have taken to using one large char array
and then only storing the pointer to any string value in the endpoint
structure. This obviously only helps if the string value is potentially
sufficiently long. I think that is what Lehane is implying below too.
In HomeVision for example there are about 2000 potential endpoints of
which any 512 are nameable and those names are 16 characters max. I
represent all the 2K endpoints but have null pointers if they are
unnamed, and additionally I only store the length of string actually
used in the name array, removing trailing space. This has saved me a lot
of memory space.
K
On 28/04/2010 09:15, Lehane Kellett (g8kmh) wrote:
>
>
> Whilst in an embedded controller application you are more interested
> in compact data structures, in a (Java, c++, C#,...) you use the
> applicable data structure to meet the program goals, making trade offs
> as required. So, if I needed 500 endpoints at 10Kb per endpoint, it
> wouldn't worry me - well, not too much ;-)
>
--------------050301010003060204030408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<head>
<style type="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
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
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>
<!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">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
One other aspect about storing endpoint data that I implemented in my
embedded devices. Where a string value (char array) is
involved
rather than using fixed length fields and hence having fixed size
structures - half of which might be empty I have taken to using one
large char array and then only storing the pointer to any string value
in the endpoint structure. This obviously only helps if the string
value is potentially sufficiently long. I think that is what
Lehane is
implying below too.<br>
<br>
In HomeVision for example there are about 2000 potential
endpoints of
which any 512 are nameable and those names are 16 characters max.
I
represent all the 2K endpoints but have null pointers if they are
unnamed, and additionally I only store the length of string actually
used in the name array, removing trailing space. This has saved me a
lot of memory space. <br>
<br>
K<br>
<br>
<br>
On 28/04/2010 09:15, Lehane Kellett (g8kmh) wrote:
<blockquote cite="mid:4BD7EEB6.6050100@xxxxxxx"
type="cite">
<meta http-equiv="Context-Type"
content="text/html; charset=ISO-8859-1">
<br>
<br>
Whilst in an embedded controller application
you are more interested in compact data structures, in a (Java, c++,
C#,...) you use the applicable data structure to meet the program
goals, making trade offs as required. So, if I needed 500 endpoints at
10Kb per endpoint, it wouldn't worry me - well, not too much ;-)<br>
<br>
</blockquote>
<br>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=2147/stime=1272456943";
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_developer/join;_ylc=X3oDMTJmdW9scXE4BF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNzI0NTY5NDM-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkdjhpNm9mBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjcyNDU2OTQz";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--------------050301010003060204030408--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|