Urban Turtle on load balanced application servers?

Edit Subject

You may be interested in this topic as it contains important information regarding running multiple application servers.

The real issue with this scenario is about the way settings are cached in Urban Turtle. We use in-proc sessions and application cache which introduce odd behaviors when multiple consecutive requests from the same user/browser are handled by different processes (even on the same machine). For now, this is not a recommended scenario, although we would really like to address this limitation in a future release.

I completely understand. We are looking for a solution for our company so that we can unify our scrum process. Currently we have about 300-350 people actively participating in scrum activities and would like to see a tool like this adopted. Please let us know if and when this might make it onto your backlog. Thanks again for such a detailed answer.

Thanks for your interest in our product. I'll add your contact (this post) to the corresponding item in our backlog.

Here's some information regarding load balancing and asp.net applications. It mentions "sticky connections", meaning users are redirected to the same server for each subsequent request. This kind of configuration could potentially work with Urban Turtle. This is something that needs configured when setting up the load balancing, which I am not really familiar with. If anyone has tried using multiple application tiers with Urban Turtle, I'd really like to hear about your experience.