views:

48

answers:

0

Hello,

I'm developing a distributed application

I have a web page (ASP.NET) to submit information.

This information needs to be handled on a specific way, so I'm using Windows Workflow Foundation. Let's call this WK1 (Workflow 1).

During this flow I need to notify certain users and get info from them aswell, so I choose to notify them using mails and redirect them to my forms on the ASP. page.

WK1 is not on same machine as the page, i'm using WCF to communicate.

Now I want to implement my notification service, and I'm considering using again WWF.

Goals: + control of this service - start, pause, resume and terminate + implement easily new types of notifications (example SMS) + the notifications do NOT need to be instant, so i'll be using queues and shedule notifications

So i'm considering implementing a state machine (singleton instance). This service will be mainly used by WK1 but might be handy for ASP page later.

So the big question is, considering the notification service is also on a distinct memory space (might be on another machine aswell) is there a way to share the same singleton instance between WK1 and ASP page? Considering all those 3 are distributed? Or I got a better design pattern to solve this problem?

Regards