> 1)Sometimes all the chain seems to stop communicating. Some GUI operation, or some interface component lock up the whole thing. If that happend in your environment, you can solve the problem by making all communication occur within a worker thread having his owen message pump. When you use multithreading with ICS, be sure to either create the ICS component within the context of the thread, typically at the beginning of thread's execute method. Alternatively, you can call threadetach et threadattach to "move" a component from a thread context to another thread context.
> I set Addr on the client and Address on the server with the IP address of > server machine, the Port on same value on both sides: is this enough to > make a connection on a LAN? For the server (listening) part, you usually set the address to 0.0.0.0 which is the default. This makes the component listening on all the interfaces. If you setup an IP address, the component listen only from that interface. When you use loopback address (127.0.0.1) to listen "locally", it wont' work with any of the physical interfaces ! That may be your problem. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Geppy Piloni" <[EMAIL PROTECTED]> To: <email@example.com> Sent: Friday, November 11, 2005 3:52 PM Subject: [twsocket] WSocket sometimes stops to receive data > > > Hi guys, > > I'm writing with D7 Pro an application composed by three different layers, > which communicate by ICS WSocket with a simple TCP/IP based protocol. > > The architecture is the following: > The first layer, call it Data Collector, connects his WSockets to the > WSocketSerevr of the second layer, call it Server, and push some records > to it. > The Server has another WSocketServer that listens for clients (third > layer) > and as soon as a client connects, the Server push the records received by > Data Collector to all connected clients. > > I have some problem I cannot resolve. > > 1)Sometimes all the chain seems to stop communicating. > I noticed that if I move/resize/minimize the windows of the applications, > often the communications stops immediately. > If I don't interact with the executables GUI, the transmissions goes for a > longer time, but after some minutes it stops anyway: sometimes few dozens > of seconds sometimes 9 or 10 minutes. > The records are quite small, from 60 to 200 bytes. > The average rate is 50/60 records every second, with peaks of 150/160: the > CPU usage is very low, I don't think is a performance problem. > I have Exception trappers in every method involved in communication > (ClientDataAvailable, ChangeState, ClientConnect, etc.) but non error is > raised. > > 2)I'm not able to establish connections on a LAN: if all the executable > are > on the same machines I connect without any problem, but if they run on > different machines. > I'm pretty sure I'm doing something wrong with WSocket properties. > I set Addr on the client and Address on the server with the IP address of > server machine, the Port on same value on both sides: is this enough to > make a connection on a LAN? > > Thank you in advance for you replies. > > Ciao. > -- > Geppy Piloni > > > > > > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be