Can't answer that directly, but there is another important difference:
Sockets allow communication between programs when both programs are already open before establishing the sockets. Connections can be arbitrarily created and dropped.
The "process commands" deal with your stack and one program which is started by the process commands. With the process commands, you have one-to-one communication.
With sockets, you can have one-to-many communication, since a single "server" program can handle connections from multiple "clients" simultaneously.
On Nov 10, 2004, at 11:00, thierry wrote:
Hi,
can someone tell me the pros and cons of communicating
between revolution and an outside program using "the open process" versus
open socket
RC> Revolution & the "outside program" must be running on the same RC> computer to use process commands. Sockets allow communication RC> between programs on different computers.
Thanks, but i was not clear enough :-) In fact, it's all about the same computer.
For instance, it's easy to use a timer with the read process with the "in time" option; how you do it with the sockets ?
Best regards, thierry
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
----------------------------------------------------------- Frank D. Engel, Jr. <[EMAIL PROTECTED]>
$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.
$
___________________________________________________________ $0 Web Hosting with up to 120MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
