Chrome connects and fetches data before you press enter or goto button.
This interesting fact I noticed when I was developing an embedded server with W5100 ethernet chip and Atmega328 microcontroller.
My setup was something like this,
I developed an embedded web server (http) and interfaced it with a debugger. It servers http client requests. This system generates interrupts for the following requests from the client side
CON: connection request
DISCON: disconnection
RECV: Received
SEND_OK: send from server
TIMEOUT: timeout
and the status of the connected socket will vary. The IP of the server is 192.168.1.179.
First I opened a firefox browser and typed th IP in address bar and hit enter.
Now I opened a chrome browser.
That means chrome is trying to create connection in the background while we are typing the address. It is sending data and receiving information in the background.
Or connecting to google search servers for a prediction of what you are typing. So before you hit the enter key the html page there behind the curtain and it is shown to you once you hit the enter key.
That means google chrome is not fast, but you are slow in typing.
This interesting fact I noticed when I was developing an embedded server with W5100 ethernet chip and Atmega328 microcontroller.
My setup was something like this,
I developed an embedded web server (http) and interfaced it with a debugger. It servers http client requests. This system generates interrupts for the following requests from the client side
CON: connection request
DISCON: disconnection
RECV: Received
SEND_OK: send from server
TIMEOUT: timeout
and the status of the connected socket will vary. The IP of the server is 192.168.1.179.
First I opened a firefox browser and typed th IP in address bar and hit enter.
- Then it got some html formatted texts from the server.
- When I pressed enter a CON and RECV interrupt occurred.
- CON - Connection request from client
- RECV - HTTP header received from the client.
- Then the server send some html back to the client - then disconnected the connection and then closed the socket.
- During the operation the socket status of the server went from
- SOCKET_LISTENING to SOCKET_ESTABLISHED (only when I hit enter in the browser) and after sending the html back to the browser the server closed the socket (SOCKET_CLOSE).
Now I opened a chrome browser.
- I typed 192.168.1.179 in the address bar.
- I didn't hit enter but in the server side (debugger) socket status changed into SOCKET_ESTABLISHED and RECV interrupt occurred The server received http header from the client.
That means chrome is trying to create connection in the background while we are typing the address. It is sending data and receiving information in the background.
Or connecting to google search servers for a prediction of what you are typing. So before you hit the enter key the html page there behind the curtain and it is shown to you once you hit the enter key.
That means google chrome is not fast, but you are slow in typing.