: Thursday, August 27, 2009 5:50 PM
To: 'U2 Users List'
Subject: Re: [U2] back to the socket problem
It appears that you are stacking instances of Program A on
top of
each other when you should be starting a client socket handler instead.
The
listen() socket function uses a single server socket
to cut down on the
phantom startup and pipe creation overhead.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen
Sent: August 28, 2009 09:53 AM
To: U2 Users List
Subject: Re: [U2] back to the socket problem
To: 'U2 Users List'
Subject: Re: [U2] back to the socket problem
It appears that you are stacking instances of Program A on
top of
each other when you should be starting a client socket handler instead.
The
listen() socket function uses a single server socket handle to wait for
all
connections
-users-
boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny
Sent: Friday, August 28, 2009 10:45 AM
To: U2 Users List
Subject: Re: [U2] back to the socket problem
The server process gets a request to run a process from a remote
machine, gets a next available port number and sends it back
I've done a lot of work with socket-based communications over the
years. The bottom line is that you simply can't do this directly
with MV platforms. Not only is it technically not possible to
hand off socket handles, but for licensing purposes most of the
MV DBMS vendors frown upon such usage
Of George Gallen
Sent: Friday, August 28, 2009 10:59 AM
To: U2 Users List
Subject: Re: [U2] back to the socket problem
I was hoping to avoid this route. Not that it would that difficult to
implement since it would only be local host that is connecting, so I
have control over both
28, 2009 1:39 PM
To: 'U2 Users List'
Subject: Re: [U2] back to the socket problem
The main benefit of using sockets is to have a single point of access
from
the client side and the ability to implement ACLs by IP and port. If
you can
queue your requests via file and perform multiplexed
Here's what I have:
Program A.
does an initserverSocket request - HANDLE1
does an acceptConneciton request - HANDLE2
does a closeSocket(HANDLE1)
executes phantom Program A (to wait for another connection).
loops through
readSocket(HANDLE2) until done (connection
://blog.all-spec.com
-Original Message-
From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-
boun...@listserver.u2ug.org] On Behalf Of George Gallen
Sent: Thursday, August 27, 2009 5:17 PM
To: U2 Users List
Subject: [U2] back
