Christian Ferrari <camauz@...> writes: > Are you exploring some interesting asynchronous pattern? > Could you tell something more about it? It might be useful to understand for all. > Thanks. > Ch.
One recent example was changing the user's authorized cookie and then 303-redirecting that user to another domain. When the load is DNS-balanced between the different servers the browser tries to stick to one server per domain, but when you 303-redirect him to another domain the browser might choose a different server. But the data is synchronized lazily between the servers, the new cookie might not work on the second server because it isn't there yet. So we register a callback to fire when the data is synchronized to all the servers (or after a timeout) and we 303-redirect the user only when this callback was fired. This of course requires the web-server to be able to pause the request and free the thread to do some other work while we are waiting for the callback. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
