bkrajendra wrote:I do not understand why u disagree..!
Basically I myself put entire Twitter Bootstrap GUI into the ESP. I'm not against it.
There is something called Thin and thick client. Its absolutely up to the need of application and thinking of developer, to decide about where to put the GUI and logic. I never said it must be done in one particular way... its just an option. Either put "GUI and Logic on ESP" or Keep only logic in ESP and make HTML5 app for desktop, Mobile, TV or any device.
For application with complex CPU hungry logic with many clients accessing ESP remotely its always better to have json api on ESP. This has been done all over internet to reduce the server load and improve throughput...!
We just look at the thing from different vantage points. You said "There is absolutely no need to put GUI in ESP" implying the general practice should be to put only a JSON API into the ESP and leaving the UI to an app or external website. My point of view is that the 128K of flash the ESP has is a great opportunity for an integrated HTML5 user interface on the ESP itself, and that that should be the default, reverting to external apps/UIs only when it's necessary.
For wireless sensor network reply I was just answering one thread n just trying to share an idea.
Sure, no worries, but what usually happens is that more people share ideas or respond to your ideas and before you know it, the thread is about wireless networks. What I ask is just to take the discussion, interesting as it may be, elsewhere so people looking for esphttpd information won't have to trudge through heaps of offtopic information.
sorry if anything has gone wrong!!!
No worries
alonewolfx2 wrote:@bkrajendra webserver with your guy too slow for first load.
Alonewolfx2: Sorry, I have trouble parsing that sentence.