What I am thinking is that if we can use Apache 2 to do it. That is, to make Apache's function beyond a request/response model.
If this API is not there, I am proposing, if possible, 1. Add an Apache API to call sub init; when starting a thread. 2. Within sub init, it calls an Apache API to disable this thread from receiving request, so that it can be used solely for scheduling purpose. Any thumb up or down on this? Steve Lihn FIS Database Support, Merck & Co., Inc. Tel: (908) 423 - 4441 > -----Original Message----- > From: Garnet R. Chaney [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 30, 2002 12:46 PM > To: Lihn, Steve; [EMAIL PROTECTED] > Subject: RE: schedule server possible? > > > Steve, > > How about another process on the same machine that > periodically accesses > > http://localhost/administration/schedule_tick.pl > > > - Garnet > > Family Friendly Search - http://www.find11.com > BidSearch - See how much others are bidding on keywords - > http://bidsearch.find11.com > > > -----Original Message----- > From: Lihn, Steve [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 29, 2002 11:57 AM > To: '[EMAIL PROTECTED]' > Subject: schedule server possible? > > > Hi, > The Apache 2 Connection handler opens up the possibility of > using it for all kinds of protocol servers. > > However, I have a wild question: Is it possible to use Apache mod_perl > for a schedule server? I.e., a server that is self existent. > > For example, I can use Apache 2 for Telnet, FTP, SMTP, or > even Telephony > Server. > But I will need a thread that processes the backend stuff, such as > maintaining > the database and message queue (more like a cron). Is this > configuration > possible? > > Steve Lihn > FIS Database Support, Merck & Co., Inc. > Tel: (908) 423 - 4441 > > > > > -------------------------------------------------------------- > -------------- > -- > Notice: This e-mail message, together with any attachments, contains > information of Merck & Co., Inc. (Whitehouse Station, New > Jersey, USA) that > may be confidential, proprietary copyrighted and/or legally > privileged, and > is intended solely for the use of the individual or entity > named in this > message. If you are not the intended recipient, and have > received this > message in error, please immediately return this by e-mail > and then delete > it. > > ============================================================== > ============== > == > > ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it. ==============================================================================
