[Opensource] servlet vs. other potential expresso containers

[larry hamel]

hi,

Expresso is currently designed to NOT assume that its containing engine is a servlet engine.

However, in many places, this obscures access to common features.  For example, casting is done to get at the servlet request in order to handle multiple params with same name.

Generality is a nice in a framework, but so is easy access to commonly-used features.

So what is the 80% case here?  How many people use Expresso in a servlet engine versus some other engine?

If we know that the overwhelming majority of users are deploying in a servlet engine, shall we optimize for that, specializing instead of generalizing?

My guess is that the tradeoff favors specialization in servlets.

larry