10531 2010-09-02 13:21:46 +0000 Load balancer: add server-specific route for polling 2010-09-03 10:38:47 +0000 1 1 1 Unclassified mobileOK Basic checker Web interface unspecified PC Linux RESOLVED FIXED P2 normal --- 1 fd fd fd oldest_to_newest 38399 0 fd 2010-09-02 13:21:46 +0000 The mobileOK Checker uses Javascript to poll for updates on the status of the requested task. Since the mobileOK Checker is now composed of a load balancer in the front end and two Web server instances in the back end, we need to make sure that the same server receives all the requests on a given task. To do this, the route to use needs to be added in a session ID, or perhaps simply in the task ID request parameter. 38449 1 fd 2010-09-03 10:38:47 +0000 Session IDs are not needed by the Checker and would introduce another useless identifier as well as the use of a useless Cookie. The load balancer only needs to be told the route it needs to follow to reach the back end server. This route may now be appended to the task ID returned by the Checker. More precisely, the "loadBalancerRoute" tells the Checker which value to use. If not set, the Checker does not append the route to the task ID. Otherwise, it returns an identifier of the form: [regular task id].[route] e.g. 2010090312345721.mobile1 Since the load balancer cannot parse parameters in HTTP POST requests, the polling task in Javascript was also updated to use only GET requests.