> > Hello, Hi, > Web applications...isn't this Internet thing just a fad? ;-) Right...... ;)
> I'm confused here. Are you talking about adding a web interface or > re-writing > Autonomy using ASP.NET? Well, a ASP.NET application doesn't do much good without a web interface, so I guess both? >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. > Porting Autonomy to UNIX shouldn't be a huge issue given the > existence of > Mono (http://www.go-mono.com/). I'm really not up to speed > on the maturity > of Mono. Does it support the idea of a service? Does it implement > remoting? Again, I think you are confusing some technologies here. Being a windows service has nothing to do with .NET. I can write a windows service in Assembly, if I wanted to. A windows service is basically an in-memory application/service that's constantly running. It can be started and stopped at will. Check out Start->Programs->Control Panel->Administrative Tools->Services for a list of services currently running on your computer. You can't port that stuff across operating systems. The concept of a 'service' is akin to a cron job or a daemon in *nix. Running as a service has its problems because that's a system-level thing. Who knows, if something goes wrong, it will not only take the web server down, but the entire server. Things like that are inherently insecure and tough to get installed by administrators onto a server machine. > We kept things as simple as possible while developing > Autonomy. We wanted > it to have three features: > > a) monitor a source code repository and detect changes > b) build each project when the source code changes > c) email the build results to the developers Yes, I get that, but the problem is that a) is explicitly tied to b), which is explicitly tied to c). There is basically no flexibility when it comes to changing the options. For example, what if I wanted to update a DB or page someone with build results? > Additionally, as Bernard mentioned, I added a remoting feature to > enable us to start builds without waiting for the next poll. Again, this is a nice feature in concept, but it fails on a couple of levels. Most notably, the service requires it's own port to run and accept commands. This isn't a problem for local in-house systems, but what about building to building or network to network? Try getting a System Admin to open a port for some "build server thingy". You will get laughed out of the room. Second, it's command line based when a web interface would be so much richer and more intuitive. > At the moment, build history is maintained by each developer > in his/her > email client. An ASP.NET based project that maintains build > results and can > start/stop/query builds via the remoting interface would be a > good addition > to Autonomy. With all status kept on a local users machine, there would be no way for the team to check build status. Why no persist this stuff to a DB? > Comments? All of these questions/problems are why I am pushing for a ASP.NET solution to be developed. If we can redesign Autonomy.NET to accomplish that, great! But if not, then I think a web based version should be built from scratch. > Regards, > Graeme Humphrey > http://www.chive.com Cheers, -Griffin ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
