Cookies
The resin tries to track the meeting user by sending the user's browser to the cookie. This cookie contains a long list of resins to be created by the ID of the meeting.
URL Rewrite
Sometimes the resin cannot create a cookie, or because the user has disabled the cookie browser, or because the browser does not support (such as HDML some browsers and wireless markup language). If the cookie can no longer be used to set up the so-called URL rewrite.
URL rewrite, rewrite each resin, and its URL is submitted to the user so that it contains a section '; Jsessionid = number; ' 。 Then for each incoming request the first thing it is to look for this parameter, if it can be aware that the meeting has been established, it eliminates the jsessionid and uses it to find the user session object.
URL rewriting requires some assistance, development, which is discussed later.
Get ServletContext, meeting, request, and response objects
