Hi Tim, Hi Trausti, > Subject: Re: OT- Client server design > From: Trausti Thor Johannsson <[EMAIL PROTECTED]> > Date: Tue, 26 Dec 2006 13:26:20 +0100 > > My 2 cents is making the connection once the app is launched and > disconnect when the app closes. It is much simpler. > When the app is idle, no data is transmitted.
Yes, this is more easy may be, although still developer should take care about "break of connection" incidents. Also to work in this way, you need set in the .ini file of Valentina Server "Timeout on client idle" to be endless, so Vserver will not disconnect idle clients. Tim, also note that Vserver Embedded has 5 default connections. If you need 100 you have choice how to do this. Please ask Lynn or me if you will need more details on this issue. > Trausti > On Dec 26, 2006, at 1:15 PM, Tim James wrote: > >> I have a Rb2006/r4 Valentina v2 app that has to service up to 100 >> individual IP connections relatively infrequently (every 3 mins or >> so) but in peak selling times every 30 seconds. The client is also >> in Rb/V2. >> >> In terms of the design employed in both the server and the client, >> which is better both in terms of server processing load and >> reliability of the connection. >> >> 1. Have all clients establish a connection and leave it sitting >> there all day ready for use, or connect/disconnect to/from the >> socket each time access is needed to the server. >> >> My concern is taking the wrong approach before I can network test >> the full load of clients on the server >> >> (Hardware currently is clients Win Xp, Server Apple X Serve) -- Best regards, Ruslan Zasukhin VP Engineering and New Technology Paradigma Software, Inc Valentina - Joining Worlds of Information http://www.paradigmasoft.com [I feel the need: the need for speed] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
