Leo,
Folks,
This is as much an application in its own right as anything else. I
propose that it moves out of Avalon (given we want to crystalise on a
core framework, impl and neat self-contained components) and goes to
Incubator. There is a minimal but decent amount of activity on this
project by Apache committers, so Incubator would be a great place to
garner more support.
Thoughts?
Where do we want Sevak to go? Will it evolve into the container-side
spec of a component-side spec? Will 90% of its classes be integrated
into the products it abstracts away from? Or will it grow in scope and
become much more than a servlet engine wrapper?
To Incubator and it remains dependent on Avalon-Framework. It is an app
not a descrete component. With the apps list collapsed, and the vote at
the same time to refocus on framework, avalon-impl and small
low-dependancy components, we moved away from my prior goal (assimilate
as many fat server concepts as possible into Avalon (the project)).
I dunno if it is possible or sensible to answer those questions right
now (go XP, bye big design ;), but I'd imagine there should be an
indication of general direction so interested peeps and incubator can
get a grip on sevak.
The XP metaphor for Sevak is...
Componentized Comodisized Servlet capable Java WebServer.
Just thoughts. I agree completely it makes perfect sense for sevak to
incubate further in incubator, so yeah, go ahead I say.
:-) I am counting that as a +1 then.
- Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
