> 2. Multi-threaded. Although the global interpreter lock may prevent
> scaling on SMP machines (hence twisteds async), I've found the
> performance to be superb in my experience. It is very responsive while
> handling simultaneous requests.
Note that Twisted's async doesn't scale on SMP machines either.
Only multiple processes will scale.
> So back to my question. Is Webware intended to be a webservices
> (web/xmlrpc/soap) app server? If not why? I understand it is not like
> twisted, supporting every protocol under the sun. It should not be. I
> think it should stay with http based protocols. But why not support
> them all? If the glove fits.
Sure -- I think Webware makes a great web services app server. My company
uses it to serve Pickle-RPC and we used to use XML-RPC. It would be great if
it supported SOAP -- it's just that nobody has done the work.
Tim Roberts wrote:
> Umm, do you realize that Webware actually implements "dynamically
> reloading modules" by "restarting the process"? The Webware process
> cannot do dynamic reloading. It just watches the file system for
> changes, and if one is detected, it commits suicide so a monitor process
> can restart it (assuming you enable that feature).
> It works quite well, so I'm not sure the difference is significant, but
> it is NOT true dynamic reloading.
Actually, even if you don't enable the "restart the appserver if anything changes" mode, Webware _does_ dynamically reload any servlets (or PSP pages) if the underlying file changes on disk. It just doesn't automatically reload any of the other modules that your servlets depend on if _they_ change.
So if you just need to tweak a servlet or PSP, you do not need to restart the appserver -- the changes do get picked up automatically.