SPUG: standard way for a web app to handle incoming email?
alwanza at yahoo.com
Tue Mar 2 18:34:34 PST 2010
WROTE (not wrong) wrote the web app (apologies).
--- On Tue, 3/2/10, Meryll Larkin <alwanza at yahoo.com> wrote:
> From: Meryll Larkin <alwanza at yahoo.com>
> Subject: Re: SPUG: standard way for a web app to handle incoming email?
> To: spug-list at pm.org, "Phil Mitchell" <phil at 2people.org>
> Date: Tuesday, March 2, 2010, 6:32 PM
> Hi Phil,
> Sorry, I don't think the same way everyone else does
> and sometimes obvious stuff eludes me and I ask stupid
> Why can't you just make the Web app do 2 things at the end
> of the action:
> 1. Send the email
> 2. Update the database
> (do you still need step 1)?
> Of course you'd have to validate user input because user
> communication directly into a database can be dangerous - I
> see you've done a good job of putting most (but not all) of
> that on the front end.
> I guess I'm assuming you wrong the Web app. Is there
> something I'm missing?
> Meryll Larkin
> Seattle Perl Users Group Mailing List
> POST TO: spug-list at pm.org
> SUBSCRIPTION: http://mail.pm.org/mailman/listinfo/spug-list
> MEETINGS: 3rd Tuesdays
> WEB PAGE: http://seattleperl.org/
More information about the spug-list