I am working on a project in which I have chosen to use xmlrpc. As I set out to look for an app server, I wanted one that would allow code changes without restarting the process(es) and one that is non-blocking. I considered building my own from the Python standard library, and I considered twisted. I'm not comfortable with twisted's deffered solution for writing non-blocking code, and neither solution would let me easily manage the server and reload modules, etc. I had used Webware before for building a website and thought it sure would be nice if Webware did XMLRPC. And lo and behold, to my delight, it does! Multi-threaded, easily managed, dynamically realoading modules. And written in pure Python. So I'm happy.
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.
-- - Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
