I've been following the CTPs and am looking forward to pushing esp. the caching part of App Fabric to our architecture this summer when the RTM is released. It's been a pleasure to work with the team on the API and meeting up with MK et all at PDC last year
was also a really positive experience.

]]>
https://channel9.msdn.com/Shows/Endpoint/endpointtv-Windows-Server-AppFabric-Server-Farm-Setup#c634112498860000000
Fri, 04 Jun 2010 12:04:46 GMThttps://channel9.msdn.com/Shows/Endpoint/endpointtv-Windows-Server-AppFabric-Server-Farm-Setup#c634112498860000000rojacobsRe: endpoint.tv - Windows Server AppFabric - Server Farm Setup
Is this it? Is this all there is to make your WF services run in a scaled out webfarm? With the race conditions on services and such that AppFabric resolved for you?

posted by dvdstelt

]]>
https://channel9.msdn.com/Shows/Endpoint/endpointtv-Windows-Server-AppFabric-Server-Farm-Setup#c634121052650000000
Mon, 14 Jun 2010 09:41:05 GMThttps://channel9.msdn.com/Shows/Endpoint/endpointtv-Windows-Server-AppFabric-Server-Farm-Setup#c634121052650000000dvdsteltRe: endpoint.tv - Windows Server AppFabric - Server Farm Setup
Good observation - there is a race condition on the server farm. We didn't discuss how it is dealt with in this episode but there is a solution provided. When the workflow is loaded, it is locked by the server that is servicing the request. If another
server tries to load it during that time it will fail to obtain the lock. It will buffer the message for a short time and retry periodically trying to obtain the lock. If it can't get the lock, eventually it will return an error to the calling application.