webserver - Server still process, browser navigated -


how webserver know browser no longer requires response. example:

  1. client/browser sends request
  2. web server processing
  3. client/browser moved page

when new request comes client, server kills previous thread?

each client request bound browser's response :

  1. client/browser sends request (request1)
  2. web server processing
  3. client/browser moved page (request2)
  4. web server processing
  5. web server returns response1
  6. client/browser ignores response1 (it waiting response last request)
  7. web server returns response2
  8. client/browser displays response2

clicking on several links @ same time several generate requests, time-consuming server. browser ignoring-irrelevant-response job.

to answer first question, can't know unless implement service kill old server processes. that's why web servers have timeout parameter.


Comments

Popular posts from this blog

jQuery clickable div with working mailto link inside -

java - Getting corefrences with Standard corenlp package -

WPF: binding viewmodel property of type DateTime to Calendar inside ItemsControl -