On Tue, Nov 27, 2001 at 10:35:43AM -0500, elian@... wrote:
> >>Well, that was the case with the HTTP server that used to be included
> Webware. It was marked as experimental, but it was fast and seemed to work
> OK with simple requests. Unfortuately people kept on reporting problems
> happened as they got a little further into using it under varying
> and nobody had the time to fix it up.<<
> How about Medusa, the same server that Zope uses? This one would appear to
> be stable and tested...
Having been one of the people who had problems with the HTTPserver that
used to be in Webware, I agree we shouldn't rush to add another one.
My problem, if I remember right, was with authenticated pages. It would
hang when submitting the login info, so I was never able to view the
authenticated examples. I switched to the CGI adapter and the problem
What would it take to use ZServer/Medusa with Webware? Just identifying
which adapters work as is and which need customization?
How does ZServer communicate with Zope? Does it use a socket connection
like we do? Or does it just import the Zope modules?
Is there a reason Webware needs a socket connection between its
AppServer and a future built-in HTTP server? Or could the HTTP server
just import the AppServer and run it on its own? Would it gain any
performance advantagess? Would there be any disadvantages, besides not
being portable to other HTTP servers?
-Mike (Iron) Orr, iron@... (if mail problems: mso@...)
http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol