Connect Laptop Hard Drive To Another Computer

client server models: we have not learned anything from the past?

Enterprise networks are growing together (thankfully) to companies that are beginning to enjoy the benefits of opportunity 'to connect, at a reasonable cost, geographically distributed locations. VPN over Internet, dedicated connections or VPN built on the backbone of the ISP ... the choices are many with many advantages and disadvantages in each. The only thing that still unites the various solutions and 'capacity' of the transmission channel. Take any wholesale ADSL line: huge capacity 'of the band to download, a window minimum (256Kbps) for uploading. This is' a technical characteristic that can 'be acceptable for a company that has to sail or (already' not) use the means of electronic messaging. We see instead a necessity 'purely administrative: what company does not have a management system? In this area there are solutions of different nature and design, yet all have one thing in common: the client / server model (like the vast majority of applications).

The thing that strikes me most of the model client / server "and now 'that few seem to have learned something from the past. Think for a moment of IBM 3270 terminals, also called "Display Device" is used to access the management system resides on mainframe (server) on dumb terminals using a program text: Telnet (client). A simple model in which the user enters the data or waiting for data on your terminal server from transmitting or receiving. The model and 'excellent, and' consists of three stages: the client in which 'present the user interface, the server effectively and that' the application that processes data from the client and transmits them to it , and the database. The characteristic phenomenal 'that dozens of people could make connections using very small as the capacity' of bandwidth used by the terminals was around Kbps (yes, one) if not during the printing process (how nice, then you send ASCII data to dot matrix printers: 80 characters per line, more ' CR and LF codes or FF). Today the model and

'"presumptuously" equal, but in reality' has a basic flaw. They removed a layer from the previous model. Today the client 'interface (GUI) while the server' brutally Database. Client / Server. Just right?

No.

The problem of network connections 'that are latent capabilities and' small. The ability 'are still large and expensive to justify the need for' a 10Mbps connection to be able to access a user management system and 'almost insane. Let us not forget that the speed 'connection between two locations connected in a VPN and' equal 'to speed' maximum connection more 'slow'. Just to understand, if two locations are connected to each other in using the VPN backbone ISP, talking about wholesale connections, even if on the route there is no traffic locations can not communicate with each other in more '256Kbps. Speaking of management, this means that if a user in a home in Turin try to access the management who is in Milan will be 'available only to those 256Kbps data transfer. Each time the user then performs a user interface, the "clients" a query, forwards it to the "server" and waits for the result ... a result that is' a recordset (a set of rows generated by the database) to be played back and processed. It often happens that the database "leave" results in its memory, so each "step process" between a record and the other needs a new request for data from the client to the database and a corresponding response. In addition, the connection timeout or the latencies bring with them problems of stability 'in the connection between the client and the server, introducing a whole series of problems and inconvenience to users so (which becomes unproductive) because the management of systems (that - done - no way to solve the problem).

The solution would be to insert a "middleware" between the two layers: the client sends a request to our "middleware" (which - in the case of systems management - and 'the management application itself), these queries database (That from a technical point of view and 'connected to the database with a high-performance network) and sends the results to the client already' developed. We should not go and invent new transmission protocols for doing these operations, there are already 'a lot and are optimized for this type of activity'. From a functional point of view, well ... things change considerably. Meanwhile, the user no longer has 'the problems of slow establishment of the connection and receive / transmit data bandwidth of 256Kbps and certainly do not represent a problem (even if the end lines are in 128-Kbps ISDN backup with the user can' safely continue to work undisturbed).