|
From: synapse505 <syn...@z5...> - 2005-05-02 15:58:12
|
| Unless you use UDP or multicast broadcasts you need a "daemon" or a | "service" at one end. | You connect to the server and then send back and forth, the server can | also redirect messages to specific connections if need be. | | Trust me the echo server is a excellent place to start. The echo server is mainly for windows, it won't compile on linux with freepascal. It also doesn't show the absolute most simplest way to send a string from one pc to another, for the absolute newbie. The code Rene sent me was what I was looking for, just to get the ball rolling without having to know anything about threads or sockets. Sure I'll be interested in threads and a daemon quite soon, but newbies need an absolute basic, dumb easy application with a full client directory with a client program, and a server directory with a server program. At least, that's what always interests me .. then I get into complexities later. People may run over to Indy because of not dumb enough and basic enough examples with synapse. The echo server is confusing (i.e. where is my client? how do I get this going? why do I need threads?) Even someone on the newsgroup posted: "I downloaded it, looked at their echo demo, and was totally lost as to what was supposed to have been happening in it..." http://groups-beta.google.com/group/borland.public.delphi.thirdpartytools.general/ browse_thread/thread/6d75fd3b2cdc74ae/fedb69e0516b468e?q=synapse+indy+delphi&rnum= 14&hl=en#fedb69e0516b468e Programmers need to have the absolute stupidest example first. That's how I got my coLinux remote compiler working in only a few minutes after Rene sent me that simple code, versus 6 days of studying sockets/tcp and synapse. But anyway, I'm going to create some dumb/easy examples myself and post them up, because now I have stuff working with synapse and I got the ball rolling. |