What technology to use to make server side scheduled jobs?
Hi,
I need to make an application consists of two parts (server/client). Server should work 24 hours and doing some scheduled jobs on desired pre-configured times. Client should be able to communicate with server and let the user configure it (change some schedule or tasks). Client should not be on all the time. Turning client off should not affect server job once it is configured properly. Client could be a web-based using ASP.Net or Windows form application using C# forms or both as options for my customer.
I was thinking about using Windows Services or WCF. I don't know if one of these will help me to accomplish my task or maybe i should use both of them, I don't know!.
I have enough time to learn and practice. I would really appreciate if someone guide me on what technology will serve me better.
Thank You
I need to make an application consists of two parts (server/client). Server should work 24 hours and doing some scheduled jobs on desired pre-configured times. Client should be able to communicate with server and let the user configure it (change some schedule or tasks). Client should not be on all the time. Turning client off should not affect server job once it is configured properly. Client could be a web-based using ASP.Net or Windows form application using C# forms or both as options for my customer.
I was thinking about using Windows Services or WCF. I don't know if one of these will help me to accomplish my task or maybe i should use both of them, I don't know!.
I have enough time to learn and practice. I would really appreciate if someone guide me on what technology will serve me better.
Thank You
Éric Moreau
have a look at http://www.emoreau.com/Entries/Articles/2004/08/Interfacing-the-Windows-Task-Scheduler.aspx
ASKER
emoreau,
Thank you for sharing that link.
I am looking for a server/client relationship and just needs to know what technology needs to be used. As mentioned in the question, should I use WCF, Windows Services, etc ...
So, let me try to explain again what my application is intended to do:
Server Application:
- runing 24 hours
- doing scheduled tasks
- could be connected by clients
- could be reconfigured remotely
Client Application:
- connects to server version
- reads and sets configurations of server version
- could be created as ASP or Windows forms
I don't require you to do all that. I just needs the correct technology that I need to start with and will not be frustrated later that something is not possible :)
I am still beginner in .Net but I have some experience with other languages.
Thank You!
Thank you for sharing that link.
I am looking for a server/client relationship and just needs to know what technology needs to be used. As mentioned in the question, should I use WCF, Windows Services, etc ...
So, let me try to explain again what my application is intended to do:
Server Application:
- runing 24 hours
- doing scheduled tasks
- could be connected by clients
- could be reconfigured remotely
Client Application:
- connects to server version
- reads and sets configurations of server version
- could be created as ASP or Windows forms
I don't require you to do all that. I just needs the correct technology that I need to start with and will not be frustrated later that something is not possible :)
I am still beginner in .Net but I have some experience with other languages.
Thank You!
why isn't your client application simply connect to the scheduled task of the server?
if you start thinking of other protocols (WCF or anything else), you will need to develop the server part and the client part. Not sure it is worth it in that scenario.
if you start thinking of other protocols (WCF or anything else), you will need to develop the server part and the client part. Not sure it is worth it in that scenario.
ASKER
emoreau,
Yes, server part should not have any user interface. all configuration must be done by client application.
Thank you
Yes, server part should not have any user interface. all configuration must be done by client application.
Thank you
why do you absolutely want to have a server part? an application on a client PC can connect to the scheduled tasks of a server without having to install anything on the server itself
ASKER
my server application will do complicated tasks and communicate with other remote devices. I need a server part, so whenever I update my application, I do update one PC only. Clients usually are ASP or Windows Forms but they just provide UI and has no complicated work.
Thank You
Thank You
Ok then.
>>I was thinking about using Windows Services or WCF.
If you want a client to communicate with a server, you should go WCF.
>>I was thinking about using Windows Services or WCF.
If you want a client to communicate with a server, you should go WCF.
I hope you know this web site related to WCF: http://netfx3.com/content/WCFHome.aspx
ASKER
emoreau,
So I have to use WCF on my server part. is WCF works 24 hours and I could apply some timer in it? At the same time can I communicate with clients while timer is running and doing some work?
So I have to use WCF on my server part. is WCF works 24 hours and I could apply some timer in it? At the same time can I communicate with clients while timer is running and doing some work?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.