On Tuesday 29 May 2001 09:16, Geoff Talvola wrote:
> I'll bet some of the problems in AsyncThreadedHTTPServer
> would be easier to fix using ThreadedAppServer as the
> base instead of Async, just because it's simpler. It'll
> just take somebody's time to do the rewrite.
There's a very simple version of an HTTPServer in
the XP code I was working on. Sometime,
I intend to refactor that stuff into a series of patches
that can be used with the existing codebase. Once that's
done, and if it works OK, we could build on the HTTPServer
that comes with it.
Problem is I'm under serious pressure to get my Thesis
out of the way right now so I won't be doing that
anytime soon. TemplateServer's docs are my second
priority after the Thesis.
If anyone is interested in picking it up here's what needs to
be done to integrate the core connection delegation code from
XP:
- write a small launcher script that will read the existing config
files and feed the settings into XP's AppServer and
Application classes - probably 1 hr
- write some methods in Application for request forwarding
- write some methods in Application for plugin installation.
could probably be ripped from the existing Application
- refactor a few methods in the existing Response class
so that the alternate approach to streaming will work.
These methods are already in the XP Response class.
Tavis
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
