Breaking News

Over the Internet of Things Hovers the Specter of Legacy Code

View Comments: Newest First | Oldest First | Threaded View
<<   <   Page 2 / 2
User Rank
Re: legacy code and that "internet of things"
_hm   8/11/2013 8:45:39 AM
This looks as opprotunity for more innovation. It may happen that all three approaches will be embraced - write new code for critical apps, device auto convert utilites for some predictable code and change code manually.


User Rank
Can IPv4 and IPV6 co-exist in IOT
prabhakar_deosthali   8/11/2013 7:57:05 AM
This may turn out to be an another monster like the Y2K .

What we need is a well laid out plan for transition from IPV4 to IPV6 based networks without having to rewrite the code.

Could it be done by accepting the IPV4 addresses in a IPV6 network by padding the additional bits having a fixed pattern non-repetitive in the IPV6 address allocation.


This way we can retain the old code and the systems and they can particpate in the new IPV6 network.

May be I am oversimplifying the problem , but just a thought.


User Rank
legacy code and that "internet of things"
WKetel   8/10/2013 9:37:54 PM
The author has made a very valid point, which comes at the problem from a different point of view, but points at the same disaster, running out of memory and crashing to a halt. As Mr Anderson points out, memory is a big deal, and it is far from infinite. While I don't understand fully the differences between IPV4 and IPV6, his point about the memory problems is certainly valid enough to make one ask "is this really a good idea?" And the prospect of programs just continuing to allot memory space and then not release it does certainly describe a very real and very fatal fault in a lot of current code. And the description of the effort needed to make changes is sort of depressing, I think.

<<   <   Page 2 / 2 Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed