|
-
Aug 31st, 2011, 05:25 PM
#1
Thread Starter
Hyperactive Member
NET Remoting or WCF??
I am building a Windows Service that will need to be instructed by a set of rules that are put into a database. The service will check the rule set and continue to process based on whatever the current rule set is. My question is how I should tell the service that there is a new rule (or that a rule has been removed). I do not want the service to check the database every so often because new rules won't be added a lot. Rather, I want the new rule being entered in the database to communicate with the windows service and tell it to check the database for a new rule.
From what I have read, .NET remoting seems to be a likely candidate for this work; however, I have also read quite a bit about WCF. Personally, I think that .NET remoting might be the way to go, but I am not sure. Can anybody make a suggestion as to which they feel is better and why? As always, your thoughts and suggestions are appreciated.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|