A second round of fixes to simplify the web application setup code and provide for a connection context accessible by the application when handling web requests.

This commit is contained in:
wcrisman
2014-07-11 12:32:03 -07:00
parent 07b8c2ff8d
commit 2b035e092c
13 changed files with 381 additions and 374 deletions

View File

@@ -18,9 +18,9 @@ import com.foundation.web.interfaces.IResponse;
public final class FrameworkController extends WebRequestController {
private static final Integer INVALID_CLIENT_ID = new Integer(0);
/* (non-Javadoc)
* @see com.foundation.web.IWebRequestHandler#processRequest(com.foundation.web.interfaces.IRequest, com.foundation.web.interfaces.IResponse, com.foundation.web.SessionData, com.foundation.web.SecureSessionData, com.foundation.web.interfaces.IConnectionContext)
* @see com.foundation.web.IWebRequestHandler#processRequest(com.foundation.web.interfaces.IRequest, com.foundation.web.interfaces.IResponse, com.foundation.web.SessionData, com.foundation.web.SecureSessionData)
*/
public void processRequest(IRequest request, IResponse response, SessionData sessionData, SecureSessionData secureSessionData, IConnectionContext connectionContext) {
public void processRequest(IRequest request, IResponse response, SessionData sessionData, SecureSessionData secureSessionData) {
String result = null;
//Note that all calls to this method within the context of a single session are single threaded - the session's request handler is used by the web application to thread the requests on the session's thread.//