The first real type of application server I've used was Tomcat. I think
webware is neat, but I do have a couple of questions.
How come webware doesn't use a similar structure like tomcat?
tomcat/
bin/
lib/
otherTomcatDirectories/
webapps/
webapps/HelloWorld
I was reading the
> Why not gear webware towards the standards tomcat and jetty follow? Doing
> so would woo over some Java programmers looking for a lighter server to
> create applications.
Maybe this is something we can consider in a next major version where we
decide we can break things. It would be also good t
perhaps then, there could be a fork as a side project. It is only
restructuring how the files are located, and perhaps a coulple extra
features, like.. eggs perhaps for packaging apps, or pwars.
I'd certainly be interested in just forking Webware to see if people like
it as an experiment for futur
tsume wrote:
> I'd certainly be interested in just forking Webware to see if people like
> it as an experiment for future development of Webware.
You are free to do this, but I suggest to wait until 1.0 and the planned
big code clean-up is released (as I said, the idea is to require a
modern Pyt
