I've written a Windows Service which does some of the same things, and the general idea I used, was:

- Started a simple C# Windows Service project to do the basics

- Used timers in this project to call up functions from the F# library doing the heavy lifting

- Had a database table representing the queue, piping the entries from this table into a function which put it on the "in code" queue

- The in code queue was a MailboxProcessor, with partially applied functions in async blocks

I'll see if I can make a simpler example out of it - stripping out the business specific - later :)

By on 9/14/2010 2:48 AM ()

Is this service to run in a different process?

I guess not - so to my mind comes the MailboxProcessor and the Async-blocks in general. There should be everything you need.

If you want more detailed responses please try to focus a bit more on concrete problems. The way you asked this questions makes it a bit hard to really answer in a helpful way without writing the hole thing yourself.

By on 9/13/2010 9:48 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper