from your unix box issue (make a script for frequent use; target box have to be some kind of unix with shell access over ssh):
$ ssh name@server -L A:B:C
where A is local port (number, bigger than 1024 for non root), B is computer you want to read from (with POP3 or IMAP server running), C is 110 for POP3 or 143 for IMAP.
Now set your email agent to get mail from 127.0.0.1 at port A with desired protocol.
For non-unix users, use some ssh client, most can do this too (RTFM).
Yust wonder when the people will realize that adding buttons to the mouse is meaningless when we have 100 or more keys on keyboard. Or will mouse morph to mouse-keyboard in near future?
you just use WaitForObject() or WaitForMultipleObjects() on EVERY type of handle.
Oh, don't forget that WainForMultipleObject have hard limit of 64 maximum objects to be wait at once. So it is useless for web servers, you need then to use the threads anyway to be able to work with multiple clients. Linux's select is better for this.
You are right, but then, they may easily by legislation (proposing such law) force people to use their backdors. It's easy - there are alresy hooks for them!
Or big memories (static, no capacitors). Wasn't there article about solid state memories as replacement for harddrives on /. recently?
from your unix box issue (make a script for frequent use; target box have to be some kind of unix with shell access over ssh):
where A is local port (number, bigger than 1024 for non root), B is computer you want to read from (with POP3 or IMAP server running), C is 110 for POP3 or 143 for IMAP.
Now set your email agent to get mail from 127.0.0.1 at port A with desired protocol. For non-unix users, use some ssh client, most can do this too (RTFM).
It should(?) be
$echo -e "0123...................
I didn't ran this anyway.
Yust wonder when the people will realize that adding buttons to the mouse is meaningless when we have 100 or more keys on keyboard. Or will mouse morph to mouse-keyboard in near future?
Oh, there must be a prior art.
Oh, don't forget that WainForMultipleObject have hard limit of 64 maximum objects to be wait at once. So it is useless for web servers, you need then to use the threads anyway to be able to work with multiple clients. Linux's select is better for this.
It does work with folowing compilers:
You are right, but then, they may easily by legislation (proposing such law) force people to use their backdors. It's easy - there are alresy hooks for them!