From richard at imagecraft.com Thu Nov 13 00:09:08 2008 From: richard at imagecraft.com (Richard Man) Date: Thu Nov 13 01:12:10 2008 Subject: [Icc-430] Polling for the Future... TCP/IP stack Message-ID: <200811130912.mAD9C7sE083395@mail.imagecraft.com> Now that eMOS for AVR (http://www.imagecraft.com/pub/emos_avr.pdf) is in beta, time to polish off the crystal balls some more. I have a consultant looking at CANLIB for AVR already. I'd think that a robust, fast, small, full-feature TCP/IP stack is high on the list of things we should do. Problem there is there are 4 qualifiers there, and as they usually say, you have 2 out of 3, or 3 out of 4. So what features would you want in a TCP/IP stack? A compiler tie-in is that someone suggested that we provide some sort of API so that a program can take a web page HTML with embedded references to C variables, e.g. ...// html stuff ... .... @foo:bar ... where bar is a local variable in foo, and the API would expand the value at runtime. I am not sure what kind of variable reference we can allow yet, but you get the idea. Yay or nay? Comments and suggestions always welcome. // richard blog: On-line orders, support, and listservers available on web site. [ For technical support on ImageCraft products, please include all previous replies in your msgs. ]