> >> Is anyone else using independent perl processes in a web app, or have strong > >> reasons not to? > > I use them for quite a few things. fork/exec works nicely in perl > (on unix at least), allows me to write daemons for most things. >
Sure, our network is supported internally by a DNS daemon written entirely in perl which supports all standard TCP/UDP queries, frontended inside by an extensive web app interface and backended by a sql server to store the data. It does all the normal daemon stuff, forking and keeping track of it's kids, etc... What appears to be the primary NS's at our site actually query the inside DNS for their updates. Modifications to the NSDB via the web interface are pushed out to the primaries in real time within a few seconds. This has been running for several years, never even a hiccup. There are a multitude of other daemon and daemon like processes that support automatic updates for a variety of speciality web sites that reside on our servers. many of these processes are spread across multiple machines, each doing their little piece to complete the puzzle -- all written in perl for the stand-alones or mod_perl for the web apps. Michael [EMAIL PROTECTED]
