About the Application Server: server information and hardware keys
Posted by: admin
Development:
Communication between machines is established using sockets. Once such a communication, information travels in packets distributed with a size of about 4 kb (approximately). For example, a data set of 400 kb distributed in some 100 travel packages.
Sockets lead, among other parameters, the IP source and destination IP, so you always reach your destination, if a node fails in the other communication nodes are interrogated to ensure delivery.
Once the communication (socket), the time information packets used in traveling is the same regardless of which occupy 4 kb or less. It is in the socket where it slows down communication, and that once the transfer of information is rapid, taking more or less along the canal by the traveling data (1k sending email is
almost equal to 4k).
Furthermore, in a local network as long as a socket used to travel is about 10 ms, while over the internet around 150-250 ms, hence the requests via the Internet are much slower: it produces a delay, and therefore should generate as few sockets as possible: we must optimize our applications.
There are several factors that increase the number of sockets created, such as grids in which data are captured meditate indirect pointers. For example, if the Internet through a grid with data from the same table, generated two sockets, one for the request and another for sending data, so that the grid is presented in less than a second. However, if we captured records generated by an indirect pointer registers as many sockets are present, so if we find 100 entries, the grid takes 25 seconds to appear.
To control how many sockets generated using a visual object (a form, a process, a grid, a menu, a box, any object), and optimize power, we can make use of the About window ... available in the application server. In the context of number of connections we have made of the data connections or sockets VATP generated by the server. To prove it, isolate the visual object that we want to check, checking on the application server that has the effect on the number of packets sent to execute the object.
We must keep in mind, finally, the wire generates a control packet or socket in the time specified in the configuration of the browser iRunner.
Related Articles
Packet loss or sockets in Windows XP or 2003 Server
What is the thread of control?
Optimizing the size of transactions
About the Application Server: server information and hardware keys
When assessing the conditions of visibility and active and important for the optimization of my application?
Loss of new sockets after Windows updates

