Home/ Questions/Q 6802417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T19:13:15+00:00

i have a WCF service which Monitors a Particular Drive and Creates a New

  • 0

i have a WCF service which Monitors a Particular Drive and Creates a New Folder weekly which i am using as a Document Storage

i have many Drives configured for Document Storage and i have to Monitor which Drive is Active(only one drive can be Active at one time ) and on Weekly Basis i have to Add a new Folder in My Active Drive at a predefined Path
provided at the configuration Time.
The Client can make any Drive Inactive or the drive can become Inactive if it is Full and i need to make another Drive Active dynamically using a Service based on priority for example
i have following drives
drive A priority 1 Active yes
drive B priority 2 Active no

if A Becomes Full i have to Make Drive B as Active

Now should i Implement a WCF Service in IIS or as a Windows Service as My Program Will Watch has to Perform Many Actions Like check the drive size and make another drive Active and send Updates in the Database

Which is a Better Way IIS or Windows Service

I need A Service which Get the Information about Drives path From the Database and I have a Configuration WIndows Application which needs to communicate with this Service also to check the drive path and Check the size if it is invalid Application will not Configure the Drive Path and if it is valid it will keep the entry in the Database and any client can have multiple directories and only one directory will be Active So that i can Store Documents in it

What about the Performance and can i configure WCF for IIS like IIS does not Refresh the Application Pool as i want my Service to Run periodically say every 30minutes – Nitin Bourai just now edit

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It seems to me a better architecture would be to have a service responsible for persisting your Documents, it can then decide where (and how) to store it and where to read it from based on who’s requesting it / how much disk space is available etc. This way all your persistance implementation details are hidden from consumers – they only need to care about Documents, not how they are persisted.

    As to how to host it… there is lots of useful information out there documenting both:

    IIS : here
    Windows Service: here

    Both would be more than capable of hosting such a service.

    • 0