> >It would be virtually impossible to write an > > ASP.NET version of Autonomy to poll a source repository, etc. > > given the fact > > that any ASP.NET application is inherently stateless. > > Whoa, I think we are talking about different things. What do you mean when > you say 'stateless'? Are you talking about a session or an application? > Regardless, it is entirely possible to build an application like that. It > has nothing whatsoever to do with state. How do you think CruiseControl > accomplishes it? That is a JSP/Servlet application. We wouldn't need to > keep track of users sessions.
The real problem here is that the ASP.NET app isn't started until the first hit to the application. IIRC, they're also spun down if they havn't seen a request in a bit. For an application that needs to poll a source code repository at a specified interval, this isn't really all that wonderful. You don't have good control over when it starts polling and you have less control over when it stops. You don't really want to have to ping the web page that kicks off your build every now and again. That's no fun. The point here is that you need something to keep your process alive, and for Autonomy, they chose to use a Windows service. As was mentioned before, the code needed to wrap up a reusable lib in a service is really pretty minimal, so you could easily host this thing in some other non-transient process. This could be a process you run personally, or a process that gets run via cron over on other platforms. It doesn't really matter. You just need some host to get the thing up and running such that it polls and does it duty at regular intervals. Does that make sense? --b ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
