From: tsume <ts...@ts...> - 2007-03-22 08:05:35
|
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 wiki, and it goes to say how people shouldn't place their apps in the webware directory so people won't get confused about app vs webware. Wouldn't this be solved if there were just a webapps directory? 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. Just my thoughts over my early use of Webware Thanks |
From: Christoph Z. <ci...@on...> - 2007-03-22 11:30:55
|
> 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 to use the features of Python eggs instead of Webware's peculiar Plugin-concept and to make WebKit more central (in the beginning, it was only one plugin on par with CGIWrapper and others that might be developed). But I still like Webware's idea of having one central installation and separate "working directories" with Webware applications that you can install everywhere (e.g. in user's home directories). In the last versions, the working dirs have also become relocatable, i.e. you can simply move them around from user A's home to user B's home. By the way, TurboGears and Django do it similarly. Webware's MakeAppWorkDir command corresponds to tg-admin quickstart or django-admin startproject which also create separate dirs anywhere. Anyway, remember that Webware was developed at a time when there was no Tomcat (only JServ and the servlet concept were already there I think) and Python was version 1.5.2 or so. Now we have already many Webware applications running which still need to be supported, so if we ever break things, we would do this in a new 2.0 branch or so, and still try to not break things without very good reasons. And just following standards from the Java world are not good enough reasons for us Pythonistas, otherwise we would be happily using Tomcat ;-) -- Chris |
From: tsume <ts...@ts...> - 2007-03-22 16:58:05
|
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 future development of Webware. On Thu, March 22, 2007 3:30 am, Christoph Zwerschke wrote: >> 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 to use the features of > Python eggs instead of Webware's peculiar Plugin-concept and to make > WebKit more central (in the beginning, it was only one plugin on par > with CGIWrapper and others that might be developed). > > But I still like Webware's idea of having one central installation and > separate "working directories" with Webware applications that you can > install everywhere (e.g. in user's home directories). In the last > versions, the working dirs have also become relocatable, i.e. you can > simply move them around from user A's home to user B's home. > > By the way, TurboGears and Django do it similarly. Webware's > MakeAppWorkDir command corresponds to tg-admin quickstart or > django-admin startproject which also create separate dirs anywhere. > > Anyway, remember that Webware was developed at a time when there was no > Tomcat (only JServ and the servlet concept were already there I think) > and Python was version 1.5.2 or so. Now we have already many Webware > applications running which still need to be supported, so if we ever > break things, we would do this in a new 2.0 branch or so, and still try > to not break things without very good reasons. And just following > standards from the Java world are not good enough reasons for us > Pythonistas, otherwise we would be happily using Tomcat ;-) > > -- Chris > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss > _______________________________________________________ email: tsume [at] tsumelabs [dot] com phone: 907.399.2337 http://www.tsumelabs.com - software and web site design |
From: Christoph Z. <ci...@on...> - 2007-03-22 17:44:52
|
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 Python versions and get rid of a lot of old garbage). After the clean-up it will much easier to implement new ideas etc. It will be difficult to merge if you do it now and *if* people really like it. -- Chris |