May 19, 2009 at 11:34 PM
Edited May 19, 2009 at 11:46 PM
I've been tasked to find a cheap solution to distribute session handling within a .net 3.5 application across multiple barebone IIS servers. It seems that most of what is offered for free (excluding NCache, i need more than 2 servers.. and their support
for 3.5 isn't quite clear) doesn't provide a session management solution that is redundant (or fully implemented)...
So from my last 3 hours of research i am still unclear how some of these solutions work; Its a simple concept nonetheless on the IIS side, however going to implement something like repcached. memcached and the memcached providers seems to raise a lot of
1. Can i use repcached+memcached with the memcached providers?
2. if yes, does this solution provide a redundant method to distribute the sessions among multiple memcached servers? Is there any additional configuration i need to do other than list the multiple memcached servers in the config?
3. If no, please explain why; this is where i am having dificulty understanding the over all setup and how these providers work.
4. either way, is there code changes required in my application by using the memcached providers?
I think i am on the right track, but we'll see. Appreciate any help on this :)
thanks a lot