#include <Dhcp.h>#include <Dns.h>#include <Ethernet.h>#include <EthernetClient.h>#include <EthernetServer.h>#include <EthernetUdp.h>#include <util.h>
i dont know if it always has been like it, but from programming perspective it seams good.You see all libraries for various sub parts of TCP/IP setup.As a programmer you can decide if you really want them.For example if you use a static IP adress you can omit DHCP by put a mark in front of it //And most services dont rely on udp, as most connections are tcp udp is for broadcasting and packets can be missed without problems (used in voice over ip youtube etc).DNS well ... you might try to mark it out and see if your code still works.Not sure if you need it, its a lookup service to get a remote IP, but your connecting clients allready have an ip adres so as long as your solution doesnt have to resolve www.somewhere.com/my.data.jpg etc.. it might work without it.And if your solution only has a server role (providing data on request)..a client might not be needed too.So despite i dont have a network add on, from a programmers look it makes sense, and its perfectas now you can mark out the code you dont need, and thereby use less memory on the arduino
Thanks! Given that I know very little about what I am doing I suspect that I will just leave it all in and hope that the compiler optimizes all of the unnecessary code away.
Quote from: jerseyguy1996 on Sep 03, 2012, 12:46 amThanks! Given that I know very little about what I am doing I suspect that I will just leave it all in and hope that the compiler optimizes all of the unnecessary code away.Setting up a web server that receives commands from android os is a pretty deep task to get involved in IMHO. If you don't know the basic ethernet stuff your in for lots of learning and many hours of reading. :-)Should be fun! Good luck.