Salil G. wrote:
I want to know what is the basic nature of a webrick.
Actually i create two instances of my application on my pc one on a
MOZILLA and second on a INTERNET EXPLORER.
on MOZILLA i uploaded 10 files and on INTERNET EXPLORER i upload only 1
But it takes same time on both browser and page loading stop at the same
i would like to know how webrick recognised who’s request.
I suspect you are asking how TCP/IP works.
host -> port -> sockets -> connections -> packets
…is the hierarchy of containers. The host is //localhost and the port
either :80 (invisible) or :3000 (explicit).
Webrick “listens” at a port until a client creates a socket and makes a
connection. The connection then persists, and another client can connect
same port. (El Goog will lead you to many details of [socket listen]
A connection is like a virtual pair of wires. The server and client
by sending and recv’ing messages, and the connection protocol cuts these
packets. Because Webrick only messes with one packet at a time (again,
speaking!), and because the connection layer stores the actual server
information, Webrick can handle multiple browsers at the same time.