1. socks
Hi all,
<rant mode on>
Remember all the stuff we had to do 10 yrs ago to get a file off a hard
drive? We had to spec the fat cylinder, the head to read from, the amount of
bytes to read, starting at what sector,, then parse that to find the file
name and location, then send a head reposition command, change heads,
allocate a space on the hd controller card to save data, get some bytes into
that space, etc etc etc? And now we use " open(filename,r/w) " and
"read(filename)". Why can't we do the same with sockets in Eu? Why can't we
use all the dos file commands, but directed at a socket?
I am *so* frustrated at windoze. So far, i have 4 programming environments
that use DDE and allow access to the winsock,, and so far, no one *i* know
can get a program written in any one of those languages to talk to the other
language in either DDE or socks. Perl and mirc talk to each other in a
limited way. Nothing talks to turbo pascal but turbo pascal. I haven't even
begun to try win_msgs, the one app i want to talk to won't do those.
Obviously, linux won't use win_msgs. All the languages use totally diff
methods to use DDE/socks, and nothing seems compatable. GRRRRRRRRRRR. For
instance, they will all go to a web page and download it, or download my
email,, but they refuse to talk to each other on the same puter! For awhile,
it looked like i was being forced to use several languages, passing data
from one to the other until the msg was sent and recieved, and that is so
totally stupid, given todays's technology.
Some folks i know on irc use *nix, win3.1,95,98,2K, dos, apple, amiga,,,,
and since they have all asked for the same piece of code from me, i was
hoping to use a common interface to all their OSs, or as common as possible,
so their irc client could talk to my code. And since they are all online,
internet sockets seemed to be the way to go.
Has someone written a Eu include file that has "winsocks made friendly" in
it? Can i *please* have it?
Kat,
shedding furiously.
