I'm hoping for faster response than once a minute, but I don't want to have a thread wasting a lot of resources polling too frequently. Which is why Id like it to be asynchronous/event-based. The AOLserver side wouldn't use any resources until explicitly called upon to do so. I'd settle for something using fileevent if the db and nsd shared the same filesystem, but they don't. I'd be up for trying to figure something out with ns_sock if I could be assured that postgres would have some way of opening up a socket and dumping data to it when triggered by a db event. I think I know enough about Oracle to cobble something like that together.
-Titi -----Original Message----- From: Tom Jackson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 12, 2006 12:58 PM To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] Handling db events in Tcl I wrote an OpenACS module, which worked on Oracle and pg called cronjob. Once per minute it queried a table, ran the sql (if any) and then ran the tcl script (if any), and sent an email report (if there was an email address). ... Remainder deleted -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
