On 1/20/11 11:10 AM, Heiko Braun wrote:
On Jan 20, 2011, at 6:02 PM, ssilvert(a)redhat.com wrote:
>> It's not reinventing the servlet API, it's using an alternative one
>> that accomplishes then same thing but with minimal overhead.
>
Let's get back to more concrete requirements.
+1. Once we know what services are needed, it's a lot easier to figure
out which of our process types can provide those things. Ideally any of
them (except ProcessController) could, as that provides greatest
flexibility.
BTW, we need to keep in mind that the console needs to work in
standalone mode as well. That doesn't rule out a very lightweight
approach though.
I already suggested a discussion about security to begin with.
If any of those identify a dependency on the servlet API, or reveal
that supporting libraries
that depend on the servlet API help us achieving our goals with less work, then we should
consider a servlet runtime.
If nothing of that is the case, fine, then proceed with the embedded server approach.
Another thing that we might consider it configuration of the HTTP endpoints.
TLS has been mentioned. How would that work on embedded HTTP? How would you specify
and use certificates? Would we need to write all that on our own?
Might look trivial, but simple bit's easily add up to a pile of work.
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat