I am sure people are bored with all this socket talk, can I email you
off list because I am missing something between your web page
documentation and what you said below
dougc
Rex Gozar wrote:
On windows, u2pipe uses wininetd; on unix or linux it can be used with
either inetd or xinetd (with xinetd you can limit the number of
simultaneous connections; pending requests get queued.)
I'm not sure I understand your question, but wininetd/inetd/xinetd can
listen on any port you specify, receiving raw requests from any system
and sending back any kind of response data. So the "requester" (i.e.
client) can be a browser, web server, or ANY other program that can
interact with sockets.
While you can write a socket listener in Universe basic, it can't be
completely fault tolerant; the process can block or hang.
Wininetd/u2pipe sidesteps the issue by spawning a new process for each
individual request.
rex
doug chanco wrote:
is it tied to wininetd/the client? (could I for example just open a
raw socket to whatever port I bound it to and send/receive data from
any system)?
from what I can gather this is tied to the client system, which makes
sense since you refer to it as a way to connect a web server to a
pick DBMS
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
