locked
In Asp.net ,http work is get ,set and forget. RRS feed

  • Question

  • When we are sending a request to server , we know that the property of HTTP is get ,set and forget, so when again we are send a request to server within same application how the server identify that which application's request is for this and how the server will process.

    please help me out.

    Thanks a lot...

    Thursday, December 6, 2012 5:43 AM

All replies

  • I think by the cookie.  An IE webbrowser will send a unique cookie with each webbrowser application when it is originally connects to the webpage.  The server must keep track of the cookies.

    jdweng

    Thursday, December 6, 2012 7:08 AM
  • Thanks Joel,

    But if we are not using cookies or sessions. then any alternative way please suggest me.

    Thanks for your reply......

    Thursday, December 6, 2012 8:16 AM
  • A connection consists of a source IP address, a destination IP address, and a port number.  You can have only one connection with all three parameters the same.  When a server has HTTP connection from different computers (source IP) you have a different connection for each by by IP address.  When you have two connections from the same computer each application on the computer will get a assigned different port number.   The IE explorer and any client will use port 80 or 8080.  The servicer on the server when a connection is made need to use port forwarding to redirect each connection to a different port number. So from the server end, it is a unique connection for each application.

    jdweng

    Thursday, December 6, 2012 10:25 AM
  • Joel what you explain that is not clear to me.

    How IIS will know which application request was it how it will process again and to whom it will provide respond.

    could you please explain more details with one example.

    Thank you in advance........... :)

    Friday, December 7, 2012 9:53 AM
  • Your application registers for an event in windows operating System.  When the connection is first established there is a table that is build in windows that associates each port number with a process.  When an incoming datagram is received by the ethernet card the datagram contains a destination IP address and port number.  The ethernet card only looks at IP addresses that are within the IP address and mask settings on the ethernet card.  Then uses the port number to find the process that is registered for the port number.  Then the datagram is forwarded up the execution stack by the Timer Tick Service to the process.

    jdweng

    Friday, December 7, 2012 10:12 AM