1 Mar 2003 01:30
RE: Re: Emailing groups from workflow
IMHO, there are security and scalability concerns with doing this that need to be considered. The alternative to wget is to create and tear down temporary, lightweight Zope instances using Zope.app() and ZEO from a secure cluster node. Having done both this and http-poked methods, I'll never go back to wget again! Here's my thoughts: => Security: only as secure as your wgetrc file, since you store the user/pw in plain-text on some box. Using out-of-process scripts on a ZEO client in a protected cluster (assuming ZEO is running on its own, relatively secure VLAN), you are less likely to need to worry about this. => If your process being called potentially leaks memory, it will slowly kill your Zope instance. Often, a complicated process can do this, especially one that creates objects in memory that garbage collection doesn't take care of (this is less of an issue for TTW code, I think, but I have a specific app where cron'd wget is used where this is a big problem); YMMV. => With an out-of-process temporary Zope created in a cron'd script, you can do many more things than you can do TTW. The downside, of course, is you need to be (a) good with more raw coding below TTW, and (b) more careful. The upside is you get complete control over the transaction machinery, and can call unrestricted code. => Queued things like sending email, etc, won't bog down the main Zope instance. This allows you to take advantage of a dedicated node to do the heavily lifting without slowing down your site. An out-of-process Zope code example (not related to email, but you get the idea): http://mail.zope.org/pipermail/zope/2003-February/131882.html Sean(Continue reading)
RSS Feed