You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(2) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
(6) |
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(10) |
Dec
(5) |
2003 |
Jan
(8) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Stuart D. <st...@as...> - 2003-02-11 02:52:53
|
Webware 0.8 has been released. It includes includes numerous enhancements and bug fixes. Webware provides a suite of Python components for developing Web applications. It includes an App Server, Servlets, Python Server Pages, Object-Relational mapping, Task Scheduling, Session management, and many other features. Webware is very modular, and easily extended. Check out the Webware for Python home page for documentation, and download instructions at http://webware.sourceforge.net/ |
From: <ash...@ya...> - 2003-02-10 23:04:51
|
HI Titus, > What you want in PYINCL is the whole C argument for > including the > Python header directory, e.g. > > -I /usr/include/python2.2 > > Similarly, for PYLIBS, you want something like > > -L /usr/local/lib/python2.2/config -lpython2.2 > -ldl \ > -lpthread -lutil -lm > > I tried to write something to pick them out of the > Python config > settings, but it sounds like it isn't working -- > could you give > me the output of running python on > _generate_pyincl.py and > _generate_pylibs.py? > I tried _generate_pyincl.py and _generate_pylibs.py and the output was as you mentioned above. I edited the makefile substituting the output of your _generate_*.py files and all seems Ok now. I'll have to finish the install tomorrow and I'll let you know how I get on :) Cheers Adam __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
From: Titus B. <ti...@ca...> - 2003-02-10 21:55:58
|
-> First of all it's great to see that this project seems -> to be reviving. I'm really excited to have a go using -> PyWX to script aolserver. I have to admit I find Tcl a -> bit painful at times. ;) -> I'm trying to install the latest beta of PyWX on -> aolserver 3.4.2 with Python 2.2, on Mandrake 8.2 -> -> I'm follwing David Kuhlmans instructions. Configure -> seems to go OK but there are some differences in the -> Makefile that is created compared to the one that -> David describes. Instead a PYTHONDIR I have two -> undefined variables PYINCL and PYLIBS . -> -> I've tried a number of different settings for these -> two. -> -> For example i set: -> -> PYINCL = /usr/include/python2.2 -> PYLIBS = /usr/lib/python2.2 -> -> PYINCL is all the Python header files and PYLIBS is -> the Python install directory. -> -> This doesn't work. If I leave PYINCL and PYLIBS -> undefined then make complains that Python.h can't be -> found. -> -> Does anyone have any good ideas? So, these settings should be generated by 'configure', or failing that you can try using _generate_pyincl.py and _generate_pylibs.py. Of course, it sounds like those are failing... What you want in PYINCL is the whole C argument for including the Python header directory, e.g. -I /usr/include/python2.2 Similarly, for PYLIBS, you want something like -L /usr/local/lib/python2.2/config -lpython2.2 -ldl \ -lpthread -lutil -lm I tried to write something to pick them out of the Python config settings, but it sounds like it isn't working -- could you give me the output of running python on _generate_pyincl.py and _generate_pylibs.py? The HOWTO should be updated before the next release, I guess. tnx, --titus |
From: <ash...@ya...> - 2003-02-10 21:05:06
|
Hi, First of all it's great to see that this project seems to be reviving. I'm really excited to have a go using PyWX to script aolserver. I have to admit I find Tcl a bit painful at times. I'm trying to install the latest beta of PyWX on aolserver 3.4.2 with Python 2.2, on Mandrake 8.2 I'm follwing David Kuhlmans instructions. Configure seems to go OK but there are some differences in the Makefile that is created compared to the one that David describes. Instead a PYTHONDIR I have two undefined variables PYINCL and PYLIBS . I've tried a number of different settings for these two. For example i set: PYINCL = /usr/include/python2.2 PYLIBS = /usr/lib/python2.2 PYINCL is all the Python header files and PYLIBS is the Python install directory. This doesn't work. If I leave PYINCL and PYLIBS undefined then make complains that Python.h can't be found. Does anyone have any good ideas? Cheers ===== __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
From: Titus B. <ti...@ca...> - 2003-01-31 06:49:02
|
On Thu, Jan 30, 2003 at 10:18:17PM -0800, Ben FrantzDale wrote: -> I am wondering if there is a PDF version of the PyWX manual at -> http://pywx.idyll.org/manual/. Since it was generated with LaTeX2HTML, -> It shouldn't be a difficult document to produce. I often would rather -> print out a nicely-formated PDF than read a series of web pages. -> -> Regards, -> Ben FrantzDale Hi, Ben, your wish is my command ;). I already had the magic lines for the Makefile on my iBook (which doesn't have latex2html); I've checked them in to CVS, and PDF files are at http://floating.caltech.edu/~t/transfer/manual.pdf and http://floating.caltech.edu/~t/transfer/howto.pdf I'll put them on the Web site with the next release. cheers, --titus |
From: Titus B. <ti...@ca...> - 2003-01-11 00:09:38
|
Hi all, I've also added 'quixote-example.tcl' and 'quixote_demo.py' underneath the PyWX/config/ directory in CVS. These collectively run the Quixote demo; all you have to do is (a) put quixote_demo.py in your PYTHONPATH or PyWX path, and (b) 'source' quixote-example.tcl. See the comments at the top of the file for more info. Because Quixote does not yet contain my threadsafety changes, the demo isn't threadsafe. I'll fix that once 0.6 final is released. Now, back to messing with DNA... cheers, --titus |
From: Titus B. <ti...@ca...> - 2003-01-10 23:44:59
|
Hi folks, last message about this, I hope ;). I've just checked in a sample AOLserver config file for Webware: see config/webware-example.tcl in the current CVS. It will be part of the next release (1.0, I hope). If you already have Webware installed, all you have to do is point the handleWebware.py file to the right directory and then source this Tcl file on startup. Slightly more detailed instructions are at the top of the config file. Dave, do you think this should go into the HOWTO? cheers, --titus |
From: Titus B. <ti...@ca...> - 2003-01-10 18:54:39
|
Hi all, thanks to Matt and Ian's prodding, I whipped up a functioning Webware adapter for PyWX. It's available under the pywx-lib/ directory as 'handleWebware.py', and to use it you need to do the following four things: * change WebKit_dir and WebKit_base_url in handleWebware.py to match your system; * in a threaded pool config area, include the Webware directory in PythonPath: ns_param PythonPath "/u/t/software/Webware-0.7" * also add an import statement to the Setup string: ns_param Setup "import handleWebware" * add a map statement that matches the base_url you edited: ns_param Map "* /WebKit.cgi/* handleWebware.handle" That should be all that's necessary. I haven't done exhaustive testing, obviously, but it's a pretty simple script and it seems to work everywhere I've tested it. I'll write up example config scripts for both Webware and Quixote in a bit, if I have time. (Certainly before the next release...) cheers, --titus |
From: Titus B. <ti...@ca...> - 2003-01-10 18:48:08
|
A looooong time ago: On Tue, Feb 19, 2002 at 11:17:04AM -0800, Chuck Esterbrook wrote: -> On Tuesday 19 February 2002 10:37 am, Titus Brown wrote: -> > Incidentally, for the PyWX out-of-process adapter I wouldn't have to -> > change a single piece of code, were CGIAdapter a bit more flexible -> > about accepting in/out arguments (rather than assuming -> > sys.stdin/sys.stdout). ?Would you mind if I went in and added this -> > flexibility (i.e. does it seem like a bad thing to have)? -> -> Sounds fine to me. Well, I finally got around to it ;). Attached is a context diff against the current CVS that allows creators of CGIAdapter objects to override sys.stdin, sys.stdout, sys.stderr, and os.environ. This is necessary for threaded servers, because the 'sys' namespace (like all module namespaces) is per-process rather than per-thread; hence, 'sys.stdin' cannot easily be over-ridden to point to a connection-specific input handle when there are multiple connections per process. If this is confusing to anyone, all you really need to know is that the following two calls to the CGIAdapter constructor are equivalent: CGIAdapter(webKitDir) CGIAdapter(webKitDir, sys.stdin, sys.stdout, sys.stderr, os.environ) so everything should work as before, for those who don't change their code. Let me know if you have any questions... This patch is necessary for the following Webware handler to work in PyWX under threaded mode: --- import sys, os, PyWX_buffer, ns_setup from UserDict import UserDict from WebKit.CGIAdapter import CGIAdapter WebKit_dir = '/u/t/software/Webware-0.7/WebKit' WebKit_base_url = '/WebKit.cgi' def handle(conn): environ = UserDict() # necessary for .data member. environ.update(os.environ) ns_setup.create_cgi_environ(conn, environ) if not environ['CONTENT_LENGTH']: environ['CONTENT_LENGTH'] = 0 environ['SCRIPT_NAME'] = WebKit_base_url environ['PATH_INFO'] = conn.request.url[len(environ['SCRIPT_NAME']):] buff = PyWX_buffer.GetBuff() p = CGIAdapter(WebKit_dir, buff, buff, sys.stderr, environ) p.run() --- I'll check in examples etc. to the PyWX code base. cheers, --titus |
From: Titus B. <ti...@ca...> - 2003-01-10 17:03:52
|
-> Has Webware support been implemented yet in PyWX? A Webware adapter -> is one of th efeatures listed in the ANNOUNCE file in the PyWX-1.0b2 -> distribution, but after doing a few case-insensitive greps, I found no -> reference to Webware or WebKit in the source. But I did find a Quixote -> handler. Thanks. It was implemented in an earlier version, but in a Tcl file rather than in Python directly (don't ask!). I forgot to take it out of the announcement; sorry ;(. However, it's easy to write & someone in my lab needs it soon, so I will write a native Python adapter to Webware this weekend. --titus |
From: Matt C. <mat...@po...> - 2003-01-10 16:57:52
|
Has Webware support been implemented yet in PyWX? A Webware adapter is one of th efeatures listed in the ANNOUNCE file in the PyWX-1.0b2 distribution, but after doing a few case-insensitive greps, I found no reference to Webware or WebKit in the source. But I did find a Quixote handler. Thanks. -- Matt Campbell Phone: (316) 652-8727 WWW: http://pobox.com/~mattcampbell/ |
From: Titus B. <ti...@ca...> - 2003-01-10 08:23:17
|
Hi folks, I've just updated the SWIG wrapping in CVS. It hasn't been updated in over a year -- since Mike Haggerty stopped active work, I think -- and a number of minor tweaks was needed to get it to build under SWIG 1.3.17 and compile under gcc. If anyone out there is a SWIG expert, it'd be great if you could take a look at the changes to src/Ns.swig... cheers, --titus |
From: Titus B. <ti...@ca...> - 2002-12-27 10:02:34
|
We are pleased to announce the release of PyWX version 1.0b2. This is our second beta release; it is known to be fairly stable. PyWX can be retrieved from SourceForge, http://www.sf.net/projects/pywx/ The PyWX homepage is http://pywx.idyll.org What is PyWX? ------------- PyWX is a Python module for AOLserver. AOLserver is a free, open-source, enterprise-class, multi-threaded web server whose performance on dynamic content is reputed to beat Apache. It is used at many large web sites including AOL and ArsDigita. It includes an internal database API that allows persistent database connections. Python is a clean, object-oriented scripting language with excellent support for complicated data structures and great libraries for web programming. PyWX embeds a Python interpreter into AOLserver, allowing threaded execution of Python scripts--even CGI scripts--within the server process. It also allows the Python script to access almost all of AOLserver's internal API via a C extension module. PyWX supports many other features, including + Threaded execution of CGI scripts within emulated CGI environment. + Cross-connection data-persistence. + Access to AOLserver's persistent database mechanism. + Internal Webware and Quixote adaptors. + Pretty good documentation. + Object-oriented Python wrapping of AOLserver's C API functions. Almost all of AOLserver's facilities are available to Python scripts. + Full access to AOLserver's Tcl interpreter from Python, and vice versa. + Optional compiled-script caching. What's new in version 1.0b2? ---------------------------- + configuration script now works properly, documentation updated. + Fixes for gcc 3.x. + Fix for a memory leak (the last detectable one!). + Several fixes for handling POSTed multipart/form-data. + Fix for uncaught exception. + Cleanup of internal HTTP header handling. + Extreme simplification of internals, fix of a crashing bug. + Update for AOLserver 3.5. + Added a handler for the Quixote application server. + Fixed unnecessary proliferation of end-of-connection callbacks. Version 1.0b2 is a bug fix version for 1.0b1 that has been tested over the past year and a half. It is currently used in several stable projects, and there are no known bugs remaining. As a rough measure of its current performance, without optimizing the machine PyWX can deliver a trivial Python script at roughly 230-310 pages per second on a single-processor Pentium 3/500MHz under Linux, and a trivial Oracle database-querying script at about 75-90 pages/s. (The range depends on PyWX configuration.) Please check out our home page at http://pywx.idyll.org and our SourceForge project page at http://sourceforge.net/projects/pywx/ for more information on PyWX, including mailing lists, development archives, and several example pages. You may also be interested in: http://www.aolserver.com -- AOLserver http://www.python.org -- the Python programming language http://webware.sourceforge.net -- Webware toolkit http://www.mems-exchange.org/software/quixote/ -- Quixote toolkit Cheers, Titus Brown for the PyWX team. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ PyWX-announce mailing list PyW...@li... https://lists.sourceforge.net/lists/listinfo/pywx-announce |
From: Titus B. <ti...@ca...> - 2002-12-19 00:31:43
|
Hi all, I've created a 'CVS checkin' notification list to which all commits are logged; this is so that Dave Kuhlman and I can coordinate without explicit e-mails... I've also updated the installation by creating a sample configuration file that should enable people to run the included examples without much hassle; I'm going to fix a few of the examples <grin> and then add a Quixote demo, and hopefully a Webware demo too. cheers, --titus |
From: Titus B. <ti...@ca...> - 2002-12-12 20:07:04
|
Hi all, Dave Kuhlman, John Totten, and Ian Lipsky (a local sysadmin) have collectively shamed me into fixing the outstanding problems with the configure script and installation docs. I've also reorganized the directories to make things a bit cleaner. The latest version in CVS contains the following changes: * all C++ files and corresponding build stuff (configure, Makefile) moved into src/; * all Python files moved into pywx-lib/; * 'configure' script in src/ now takes two arguments: e.g. % cd src; % ./configure --with-python=2.2 --with-aolserver-src=../../aolserver-3.5.1-src Moreover, these parameters are correctly used in the Makefile. New with this update is also a mechanism to automatically figure out what libraries are needed with Python, and a couple of other fixes to the Makefile that take care of all of the problems I know about. * The INSTALL and README documentation has also been updated to reflect these changes. * Several obsolete files have been trashed -- mostly the .tcl files. Err, I think that's it. I'm going to run through Dave Kuhlman's excellent docs later today to fix what I've broken ;), and then I have to go through the doc/ docs to fix them -- that may take a little longer. Please, try it out and let me know what breaks on your system! It works fine for my RH 7.2 and RH 8.0 installs... --titus |
From: Dave K. <dku...@cu...> - 2002-12-03 01:34:12
|
Titus - Thanks much for this explanation. It worked. Super. Now I'm hoping that I can remember what I did (following your instructions) long enough so that I can write it up and add it to my how-to doc. I'll send a note when I've done so. Thanks again. - Dave On Mon, Dec 02, 2002 at 09:29:45AM -0800, Titus Brown wrote: > -> I have aolserver up and running with postgreSQL and PyWX. I have Quixote > -> running on top of PyWX without Publisher() - just enable_ptl() > -> > -> But I am not clear from your last post on the list just exactly how to > -> install the ThreadedPublisher - handler.Handle. I do have the latest > -> 0.6 Quixote with your patches and I do have the latest Handler, and I > -> do have the ns_param entry that you recommended > -> > -> Can you give me a blow by blow account of how to get it together (including > -> what you use as the handler filename.) > > Sure -- I'll start by assuming that you have a functioning CGI setup, > and can run scripts by putting them in the appropriate directory and > calling them directly, e.g. > > http://localhost/script/hello-world.py [much good info snipped] -- Dave Kuhlman dku...@re... http://www.rexx.com/~dkuhlman |
From: Titus B. <ti...@ca...> - 2002-12-02 17:30:50
|
-> I have aolserver up and running with postgreSQL and PyWX. I have Quixote -> running on top of PyWX without Publisher() - just enable_ptl() -> -> But I am not clear from your last post on the list just exactly how to -> install the ThreadedPublisher - handler.Handle. I do have the latest -> 0.6 Quixote with your patches and I do have the latest Handler, and I -> do have the ns_param entry that you recommended -> -> Can you give me a blow by blow account of how to get it together (including -> what you use as the handler filename.) Sure -- I'll start by assuming that you have a functioning CGI setup, and can run scripts by putting them in the appropriate directory and calling them directly, e.g. http://localhost/script/hello-world.py Usually these scripts are running under interpreter mode, in which a new Python interpreter is used for each connection; this avoids any sort of cross-talk between instances of the script from namespace pollution, and mimics your normal CGI environment fairly well. Now, go to your config file and make sure you also have a 'thread' pool: you should see -- ns_param Pools "interp,thread,cgi" -- if you put the example Tcl into your configuration from the INSTALL file. You're going to use the 'thread' pool, which uses a single interpreter with multiple threads to serve Web pages. Also make sure that your PyWXPath variable contains the directory with Nspywx.so and *.py (from the PyWX distribution) in it; I usually put this in 'pywx-lib/' under the AOLserver install directory: -- ns_param PyWXPath "${homedir}/pywx-lib" -- Go find the ns_section for "ns/module/pywx/pool/thread". Here you want to make sure that you have the following commands: -- ns_param Mode Threaded ns_param PythonPath "/path/to/directory/with/your/quixote/package" -- where "your Quixote package" means *your* own code; the latest Quixote from CVS should be installed, or also placed in this PythonPath (: delimited). In this same section ("ns/module/pywx/pool/thread") put the command -- ns_param Setup "import handler" -- where "handler.py" is in your/quixote/package/ and looks like the attached 'handler.py'. This file should do the following: 1. create a Quixote publisher for your app ("app"); 2. create a handleQuixote.Handler instance: _handler = handleQuixote.Handler("base_url", app) 3. define a function 'handle' that calls '_handler.handle'. Now, assuming that all worked, the last thing you need to do is map that handler to a particular URL. Again in your .tcl configuration file, under the section "ns/server/${servername}/module/pywx/pool/thread", put the command: ns_param Map "* /base_url/* handler.handle" And voila, you should be done! Start AOLserver up and try going to /base_url/. Stepping back a bit, the object is to get /base_url/* mapped to a function that calls the appropriate publish() function on your Quixote publisher object. Most of this is just path setup and code setup to do that... Now that I've written it all out, I'm not surprised you were having trouble ;). I will try to put together a demo handler this week... -> And could you give me a little foresight into just how you can deal with the -> database handles that go with the threads? I use a Queue (Python std lib) to synchronize around grabbing database handles from a common pool. I don't use the standard ns_ methods for getting the handles in the first place, tho; I use 'psycopg' (initd.org/) instead. I can send you some source if you like. I hope all this helps ;). --titus |
From: Titus B. <ti...@ca...> - 2002-11-25 18:08:55
|
-> I'm trying to use your Quixote adapter. I've put off asking for -> help, trying to push myself to learn enough about Quixote's -> execution model so that I could figure this out for myself. Well, -> I think I do understand more, but still could not figure this setup -> out for myself. So a few questions: -> -> I put the adapter in: -> -> aolserver/servers/server1/modules/python/handleQuixote.py -> -> Right? It needs to be in PYTHONPATH, or PythonPath, or some place where it can be imported. -> Now, what should I do with each of: -> -> import handleQuixote -> handler = handleQuixote.Handler(base_url, app) -> -> Do I put it into a Quixote driver script? Something like the -> following in aolserver/servers/server1/pages/qtest1.cgi? -> -> #!/usr/bin/env python -> -> from quixote import enable_ptl, Publisher -> import handleQuixote -> -> enable_ptl() -> app = Publisher('qtest1') -> app.read_config("qtest1.conf") -> app.setup_logs() -> handler = handleQuixote.Handler('qtest1', app) -> -> Is that right? This also needs to go into an importable file, NOT a CGI script. -> If so, where do I put: -> -> handler.handle(conn) -> -> And is conn what I'd get from calling: -> -> conn = Ns.GetConn() handler.handle should be called directly from PyWX; the configuration line looks like this: ns_section "ns/server/${servername}/module/pywx/pool/thread" ns_param Map "* /canal/* handler.handle" (for mapping '/canal' into Quixote). -> Perhaps you could send me your latest Quixote PyWX adapter. I -> notice that the version I have calls: -> -> ns_setup.create_cgi_environ(conn, os.environ) -> -> This was missing from the version of modules/python/ns_setup.py. I -> I down-loaded the CVS version of PyWX, and found it in that version -> of ns_setup.py. Is that what I should be using? -> -> In case it matters, I'm using: -> -> Quixote-0.5.1 -> aolserver-3.5.1-src -> PyWX from CVS -> Libranet Debian GNU/Linux - Linux 2.4.19 -> -> Thanks in advance for help. I'll check in the version I'm using with my latest Cartwheel stuff once I verify that it actually works with the latest CVS version of Quixote; it requires Quixote out of CVS, because I had to <sigh> modify Quixote to support multiple threads of execution. Attached are two files: my development environment config for Cartwheel, and the quixote handler I'm using in it. Thanks for slogging through all of this -- you're shaming me publicly enough that I may do something about it ;). cheers, --titus |
From: Dave K. <dku...@cu...> - 2002-11-21 05:10:58
|
Titus - I'm trying to use your Quixote adapter. I've put off asking for help, trying to push myself to learn enough about Quixote's execution model so that I could figure this out for myself. Well, I think I do understand more, but still could not figure this setup out for myself. So a few questions: I put the adapter in: aolserver/servers/server1/modules/python/handleQuixote.py Right? Now, what should I do with each of: import handleQuixote handler = handleQuixote.Handler(base_url, app) Do I put it into a Quixote driver script? Something like the following in aolserver/servers/server1/pages/qtest1.cgi? #!/usr/bin/env python from quixote import enable_ptl, Publisher import handleQuixote enable_ptl() app = Publisher('qtest1') app.read_config("qtest1.conf") app.setup_logs() handler = handleQuixote.Handler('qtest1', app) Is that right? If so, where do I put: handler.handle(conn) And is conn what I'd get from calling: conn = Ns.GetConn() From looking at ns_setup.py, it looks like conn should be an PyWX/Ns thing, not a Quixote object. Perhaps you could send me your latest Quixote PyWX adapter. I notice that the version I have calls: ns_setup.create_cgi_environ(conn, os.environ) This was missing from the version of modules/python/ns_setup.py. I I down-loaded the CVS version of PyWX, and found it in that version of ns_setup.py. Is that what I should be using? In case it matters, I'm using: Quixote-0.5.1 aolserver-3.5.1-src PyWX from CVS Libranet Debian GNU/Linux - Linux 2.4.19 Thanks in advance for help. - Dave -- Dave Kuhlman dku...@re... http://www.rexx.com/~dkuhlman |
From: Titus B. <ti...@ca...> - 2002-11-14 04:40:05
|
-> By the way, I'm very interested in using your Quixote adapter -> (which I found in an email in the email list archive). When I -> figure it out, that will be the next thing I add to my how-to -> document. Great -- I don't know what version you have of the adapter, but I will check the multithreaded one into CVS soon. Let me know if you want it sooner. And I'm very happy someone is stepping up to the plate to do some of the documentation work that I should have done... thanks! -> Thanks again for PyWX. Brent Fulgham and Mike Haggerty did an awful lot of the coding, too ;). I'm just the only one left using it! But you're certainly welcome on my behalf ;). --titus |
From: Dave K. <dku...@cu...> - 2002-11-13 23:35:47
|
On Wed, Nov 13, 2002 at 02:37:06PM -0800, Titus Brown wrote: > Very nice! I've been asked to write an article about PyWX for a magazine, > and I will hopefully revamp the Web site while doing so: do you mind if I add > a link to this on the site? Titus - You are welcome to do so. However, I'm an AOLServer/PyWX newbie. So, you may want to give it a quick scan to spot any obvious errors before linking to it. Please let me know if (OK, when) you find something I need to fix. By the way, I'm very interested in using your Quixote adapter (which I found in an email in the email list archive). When I figure it out, that will be the next thing I add to my how-to document. Thanks again for PyWX. - Dave > > thanks, > --titus > > On Wed, Nov 13, 2002 at 11:30:18AM -0800, Dave Kuhlman wrote: > -> > -> First, my thanks to Titus for PyWX. I'm a Python fan and user. So > -> having a Python interface to AOLServer is a big win for me. > -> > -> I've been working on learning AOLServer and PyWX with PostgreSQL. > -> > -> I've written up some of my experiences in a how-to document. It > -> still needs work, I'm sure. If you think it might be of help, you > -> can find it at: > -> > -> http://www.rexx.com/~dkuhlman > -> http://www.rexx.com/~dkuhlman/aolserver_howto.html > -> > -> Suggestions are welcome. > -> > -> - Dave > -> > -> -- > -> Dave Kuhlman > -> dku...@re... > -> http://www.rexx.com/~dkuhlman -- Dave Kuhlman dku...@re... http://www.rexx.com/~dkuhlman |
From: Titus B. <ti...@ca...> - 2002-11-13 22:37:11
|
Very nice! I've been asked to write an article about PyWX for a magazine, and I will hopefully revamp the Web site while doing so: do you mind if I add a link to this on the site? thanks, --titus On Wed, Nov 13, 2002 at 11:30:18AM -0800, Dave Kuhlman wrote: -> -> First, my thanks to Titus for PyWX. I'm a Python fan and user. So -> having a Python interface to AOLServer is a big win for me. -> -> I've been working on learning AOLServer and PyWX with PostgreSQL. -> -> I've written up some of my experiences in a how-to document. It -> still needs work, I'm sure. If you think it might be of help, you -> can find it at: -> -> http://www.rexx.com/~dkuhlman -> http://www.rexx.com/~dkuhlman/aolserver_howto.html -> -> Suggestions are welcome. -> -> - Dave -> -> -- -> Dave Kuhlman -> dku...@re... -> http://www.rexx.com/~dkuhlman |
From: Dave K. <dku...@cu...> - 2002-11-13 19:30:20
|
First, my thanks to Titus for PyWX. I'm a Python fan and user. So having a Python interface to AOLServer is a big win for me. I've been working on learning AOLServer and PyWX with PostgreSQL. I've written up some of my experiences in a how-to document. It still needs work, I'm sure. If you think it might be of help, you can find it at: http://www.rexx.com/~dkuhlman http://www.rexx.com/~dkuhlman/aolserver_howto.html Suggestions are welcome. - Dave -- Dave Kuhlman dku...@re... http://www.rexx.com/~dkuhlman |
From: Titus B. <ti...@ca...> - 2002-11-08 21:25:07
|
p.s. Make sure you use the latest CVS code; all code up until then had problems with multithreading under medium or high loads. You'll need AOLserver 3.5... On Fri, Nov 08, 2002 at 02:14:37PM -0500, cmulcahy wrote: -> Titus, -> -> Suppose I want a persistent resource that all pywx pages can access. -> -> Say I run pywx in single-interpreter mode. -> At startup I have the interpreter import a few modules written be me. -> -> In these modules I define resource pools ( containing database handles for -> example ) pseudo-public methods ( pseudo since you can't create private -> name-space in python such that I know ) to access them, and mutexes ( -> thread.allocate_lock() works? ) to synchronize said access. -> -> I then access in the namespace of these modules only those functions that I -> have written with public-safety in mind. -> -> Is this the general idea? -> -> -> ------------------------------------------------------- -> This sf.net email is sponsored by: See the NEW Palm -> Tungsten T handheld. Power & Color in a compact size! -> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en -> _______________________________________________ -> PyWX-discuss mailing list -> PyW...@li... -> https://lists.sourceforge.net/lists/listinfo/pywx-discuss |
From: Titus B. <ti...@ca...> - 2002-11-08 21:24:28
|
-> Suppose I want a persistent resource that all pywx pages can access. -> -> Say I run pywx in single-interpreter mode. -> At startup I have the interpreter import a few modules written be me. -> -> In these modules I define resource pools ( containing database handles for -> example ) pseudo-public methods ( pseudo since you can't create private -> name-space in python such that I know ) to access them, and mutexes ( -> thread.allocate_lock() works? ) to synchronize said access. -> -> I then access in the namespace of these modules only those functions that I -> have written with public-safety in mind. -> -> Is this the general idea? That should work just fine, yes. You should initialize the resource pools on import, to avoid initializing them more than once; apart from that, make sure you are running in multithreaded (as opposed to multi-interpreter) mode. cheers, --titus |