I have a simple VB 2008 project which exists of two projects:
1. Host - Console Application - with persistence and with remoting
enabled
2. Client - Console Application - Connects to the Host through
remoting, and schedules job.
It will be very simple to change the Host into a Windows Service
(although same principle, just easier to test as console app). In my
production application I have the Host as a Windows Service and the
Client is a WPF Application. I might (probably will) rewrite my WPF
Client so that it works in SilverLight 2.0. However, I dont know if
remoting works that easily in a SilverLight application.
I think the Remoting Samples is pretty straightforward. Two things
missing on the sample applications were the following:
1. Database Persistence (had a buddy tell me how to enable it...).
2. Direct Database Modifications (Didnt know that was an option, so I
used remoting).
Has anyone begun creating code for this? Like I said, I will probably
rewrite my Client into SilverLight 2.0 that connects directly to the
DB to modify/create the schedules. If someone has a start that would
be welcome.
Carsten
> I totally agree that we need a web application sample for Quartz.
> There's one in Java land and I can probably create a similar one with
>
ASP.NET MVC (.NET 3.5 only, thoughts?). I'm also more than willing to
> accept community contributions.
>
> The general idea to handle the scenario is:
>
> * 1-n web app installation(s) to handle administrative tasks via web
> interface and ZeroSizeThreadPool (no jobs run here)
> * 1-n windows service installation(s) to run the jobs (clustering/load
> balancing)
>
> This can be achieved using just the plain DB back-end. If we want to
> control running states of schedulers we also need remoting / UDP
> broadcasts.
>
> Cheers,
>
> -Marko
>