Orcas Durable Services

My durable WCF RESTful calculator

Pablo M. Cibraro (aka Cibrax) — Tue, 25 Nov 2008 19:00:07 GMT

A durable service in WCF is by a definition a service that can persist all its internal state across

TechDays – 2º Dia

Miguel Isidoro — Mon, 17 Mar 2008 21:49:29 GMT

Decorreu na passada semana entre os dias 12 e 14 de Março a edição deste ano do TechDays , o maior evento

TechDays – Dia 2

Miguel Isidoro — Mon, 17 Mar 2008 21:27:32 GMT

Decorreu na passada semana entre os dias 12 e 14 de Março a edição deste ano do TechDays , o maior evento

re: Orcas Durable Services

Channappa J B — Thu, 07 Feb 2008 15:35:59 GMT

Hi,

Your article is really useful for beginners who are exploring Durable services.

Found one issue with the code though. In Fig. 2, you marked TextComposer service with a "DurableServiceBehavior" attribute instead of "DurableService". This is a typo, did trouble for a while though :). Hope you can correct it.

Thanks for the post.

WCF Durable Services

Compono Technology, Inc. — Sat, 19 Jan 2008 19:36:22 GMT

WCF Durable Services

[WCF] Novità e fix del .NET Framework 3.5 e .NET 3.0 Sp1

BlogServiceHost.Create() — Wed, 31 Oct 2007 08:22:44 GMT

Christian Weyer hascritto un gran bel post riassuntivo delle maggiori novità e fix della nuova release.

Beyond the Obvious: New Features and Fixes for WCF in .NET 3.5

Christian Weyer: Smells like service spirit — Mon, 29 Oct 2007 14:47:32 GMT

With .NET 3.5 and Visual Studio 2008 being quite close to RTM these days, I thought it would be time...

[Podcast] Durable Services with WCF, WF, and NServiceBus

[Podcast] Durable Services with WCF, WF, and NServiceBus — Tue, 23 Oct 2007 21:18:47 GMT

Pingback from [Podcast] Durable Services with WCF, WF, and NServiceBus

kennyw.com » Blog Archive » Throttling in WCF

kennyw.com » Blog Archive » Throttling in WCF — Wed, 08 Aug 2007 01:04:13 GMT

Pingback from kennyw.com » Blog Archive » Throttling in WCF

re: Orcas Durable Services

Udi Dahan - The Software Simplist — Sat, 30 Jun 2007 21:24:55 GMT

I really want to post something on my blog about this, but this comment will have to do in the meantime.

Explicit state management is what scales and is robust in the face of failure. This solution seems, to me, to be lacking in those respects. It may also just be me, but the solution seems quite complex. What about something more similar to long-running workflows?

Am I missing something here?