This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Ok. Now it's time for you guys to tell me what have you done for the zero functionality release in your past XP projects... I'm just curious about how much people are obeying the "leanness" principle of "not using an appserver if it's not yet needed by the stories."
With all due respect - I think that most projects actually *never* need an appserver. Seriously.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Ilja wrote: I think that most projects actually *never* need an appserver Hmm. Depends what you mean by the overloaded term "appserver". It's a long time since I built any web application which included its own web server code. These days I just create the "application" part and deploy it to some sort of third-party server which will handle all that multithreaded HTTP stuff for me. Examples might include Apache, Resin, Tomcat, Orion etc. I think of these (and refer to them) as application servers. Do you use the term differently, or do you really include HTTP server code with every little web application?
As some of you guys might know, I'm working for a big system integrator and our projects often "require" clustering, management, fitting into this and that legacy system, satisfying the client's IT dept standards, etc. Having said that, an application server to build on is worth the trouble in most cases. Then again, it's still probably not right from the beginning when the appserver is really needed.