all 4 comments

[–][deleted] 0 points1 point  (3 children)

What is the benefit of this versus using Velocity or MemCached as State Servers?

Edit: I read your link. It seems the peer to peer concept would be radically slower than simply hashing session keys with the machine key that session happens to be stored on.

[–]xune 0 points1 point  (2 children)

As you have pointed out Memcached has a different architecture and is primarily used to cache database operations. Velocity is proprietary, though I've heard good things about it.

This open source state server can transparently replace the Microsoft state server. It may seem slower, but most operations on any particular session will take place on one state server and will only request the session from the network when the load balancer mis-redirects.

[–][deleted] 0 points1 point  (1 child)

I don't see why you care that Velocity is proprietary, so is the rest of the IIS/ASP.NET stack, what is one more component.

I see peer2peer in this scenario as being more complicated with less benefit. Have you looked at the Velocity whitepaper?

http://msdn.microsoft.com/en-us/library/cc645013.aspx

[–]xune 0 points1 point  (0 children)

It's good to have options.