??? 04/08/10 07:41 Modified: 04/08/10 07:43 Read: times |
#174905 - many clients - definitely the way to go! Responding to: ???'s previous message |
Stefan Kanev said:
These days allmost nobody cares about bandwidth True, but bandwidth has nothing to do with it - the usage will be (pretty much) the same irrespective of which end takes the "server" role. Many clients to one "web programmmer" server will be not prefferable , i think. From experience, I say that it is preferable! :-) Think about it: this is the "normal" architecture of any client-server system - the clients are many, and the servers are few. It is also the way IP networks are designed: Public (especially Static) IP addresses are (relatively) few, and (possibly) also expensive. Anyway - building/programming many clients (or servers) into end devices or interface convertors can be used only if everything is based on some standard Yes, of course. i'm just reader, who never was building such systems. Ah, there's over a thousand of my embedded client devices talking to their "web" server as we speak... |
Topic | Author | Date |
Ethernet Redux | 01/01/70 00:00 | |
The problem is, I think | 01/01/70 00:00 | |
Web type programmers... | 01/01/70 00:00 | |
Wrong way around! | 01/01/70 00:00 | |
Nice | 01/01/70 00:00 | |
How do you program it? | 01/01/70 00:00 | |
Free compiler for the new Cortex-M3 | 01/01/70 00:00 | |
RE: Free compiler for the new Cortex-M3 | 01/01/70 00:00 | |
'penalty' of no IDE? | 01/01/70 00:00 | |
Missed the point | 01/01/70 00:00 | |
Both | 01/01/70 00:00 | |
many clients | 01/01/70 00:00 | |
many clients - definitely the way to go! | 01/01/70 00:00 | |
Wiznet does TCPIP | 01/01/70 00:00 | |
... and ethernet MAC | 01/01/70 00:00 | |
Clients and servers | 01/01/70 00:00 | |
That's a "Client" | 01/01/70 00:00 | |
so | 01/01/70 00:00 |