I haven't done any web programming with Java, but I'm not sure that you'll find Mono significantly smaller or faster. Well, it probably depends a lot on the application.I'm not as much worried about the speed of the application as I am the speed of development. Comparable execution speed is good for us. Mod_mono hides the fact that it's a separate application server fairly well, except this business of having to manually restart it. But, it is a separate process from Apache.That's ok. The execution requirements of Xsp seem a lot less than that of Java alternatives like JBoss/Tomcat/Jetty et al. C# is definitely a step up from Java.Which is exactly why I'm motivated to learn more... again, I'm looking at ways to increase our productivity, and I'm testing out some of the philosophies associated with C#/aspx pages compared to Java/jsp pages. So far, I like what I've seen. There are a miriad of libraries/frameworks et al for java jsp, but a lot of that appears to be built into C#/mono already (ie: State management). I can't think of any serious issues, but you're bound to run into some minor problems at some point. For instance, I had to write my own database connection pooling routines because I couldn't figure out if it was working right in the MySQL library at the time. I also had some problems with System.Web's caching because of the way it monitors changes to files when the fam library isn't available. This has since been fixed.Good to hear. Thanks again for the response. I won't be rolling out any major application in C# any time soon, but hopefully, I'll be capable of doing it if the opportunity arises. -Dennis |
