I have a partially working HTTP server which I put on hold in favor of first
developing a CGI server. I experienced no data loss from the HTTP server so
far, but I have only been testing one request at a time. I have not yet
tried to close the multiple request loop of automatically putting the server
job back into the state of waiting on the next request or of jobbing
multiple server processes to ensure that there is no gap where incoming
requests can get lost between "listens". Is that where you are having
This reminds me of a related question I have intended to ask Bhaskar (or
anyone who knows) for a while now. What is the effect and intended use of
the "queuedepth" parameter in "WRITE /LISTEN(queudepth)"? Is that intended
for services that will be handled in sequence by a single server job? Is
queuedepth>1 compatible with a service, such as HTTP, which must be expected
to frequently overflow a queue which is apparently limited to a depth of 5?
Stephen Maher wrote:
>has anyone a working example of a Sockets server serving multiple
>requests? I have build some code based on the manual pages, but I have
>data loss from the client.. (Which is not GTM).
>Any working examples would be most appreciated.
listSanchez-gtm-core@... href="nethttp://lists.sourceforge.net/lists" target="_new">nethttp://lists.sourceforge.net/lists
Manager and Chief Developer
VMTH Computer Services, UC Davis