| ??? 03/01/08 08:35 Read: times |
#151716 - Impossible to answer Responding to: ???'s previous message |
Karandeep Singh said:
Now the questions that arise are--------
1. By which mean I should connect my terminal to internet? 2. what should be the application layer? As previously mentioned, there are many possibilities here - only you can answer these questions, since only you know your project's requirements, constraints, etc... 3. if I make each terminal a website it will be to costly that is if on a client site I hav 200 terminals then making 200 websites will be to costly. You said this before, and it didn't make sense then: http://www.8052.com/forum/read.phtml?id=151497 You still haven't answered the question! There is no reason why this should be particularly costly; Why do you think it will be? Where do you think the costs lie? 4. Now making a terminal a Web Server , I don’t know how can I use a web server terminal to make a web interface via internet to a website? There is plenty of information available on how to do this - including direct from SiLabs - see: http://www.8052.com/forum/read.phtml?id=149517 If there is any solution to my problem , please tell me? It's your problem - it's up to you to work out a solution that fits your requirements and constraints. Waiting for your reply!!! Don't just sit there waiting for solutions to fly in through your windows; you need to start doing some work - in particular studying the available internet protocols, and that large amount of existing information on internet-enabling embedded systems. Again, take a look at these tutorials on the basics of IP sockets: http://www.frostbytes.com/~jimf/pap...nsock.html http://www.frostbytes.com/~jimf/pap...ckets.html Take a look at this tutrial on HTTP: http://www.jmarshall.com/easy/http/ Review the materials provided by SiLabs, and the other links provided here: http://www.8052.com/forum/read.phtml?id=149517 |
