Hi ! > Client side : Always the message "Pending" + server name.
I don't know how you send the reply (since there are several ways to do it), but if you don't set ContentLength correctly, then the client may wait forever for data that will never comes. As you said it usually works, probable the length is set correctly. You have to verify if it is always the case. To have a better idea about what happend, you may think about installing a sniffer (there are free ones) to capture the traffic and then later check that everything is OK at the network cable. > What I describe here is not constant (too easy!) , the user can work for > some time and then it falls into this "loop". Once the issue appears, is it there for all clients or only a few ones ? Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be ----- Original Message ----- From: "Guillaume ROQUES" <[EMAIL PROTECTED]> To: "twsocket" <firstname.lastname@example.org> Sent: Tuesday, June 10, 2008 11:58 AM Subject: [twsocket] [THTTPServer] Answers blocked ? > Hi, > > we are using ICS components for a Web server, developed as a windows > service, since a long time now and everything work fine. > But we just install it in a hospital and found problems concerns answers > from the web server. > > Client side : sending a request through a form, then the browser > displays "Pending" + server name. > Server side : parse values of the requests (ListIn) and sending the > response (ListOut) > Client side : Always the message "Pending" + server name. > Server side : The process have a normal activity but the web server > seems to loop on sending, a stop / start on the service puts things in > place. > > What I describe here is not constant (too easy!) , the user can work for > some time and then it falls into this "loop". > What we see is that often happens in the morning and in the early > afternoon, testing in the late afternoon show that the service and the web > server is working properly (?), it could coincide with the number of users > on the network.... > Knowing that this is a network hospital, there are a lot of intermediate > (proxy, switch, hub, firewall), maybe their configuration block my > answers.... > > I would like to know if it evokes something to someone, just to have a > clue or a way to look for. > > For the ICS component I 'd also like know how to "get out of the blocking > loop ". > Is there a way to detect that sending failed or unsuccessful ? > Client side, I understand that it could be, as he interrogates the server, > but server side ? > > I hope to have been sufficiently clear on the description of the problem, > I'll try to have more information on the architecture of network ..... > > Guillaume ROQUES > CANYON Technologies > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be