[nycphp-talk] email system for website

Paul A Houle paul at
Mon Jan 4 14:52:52 EST 2010

Matt Juszczak wrote:
> Thanks for your reply. Actually, it's the exact opposite.  I want to 
> make the system as simple and easy as possible.  The problem is that 
> right now, we have our front end code send emails.  The developers are 
> starting to get annoyed at writing all of the logic over and over 
> again for each front end (for instance, we're in the middle of writing 
> an iphone app as well, which is a more simpler implementation, but we 
> need some sort of REST layer to facilitate communication with the 
> database).  I've been implementing stored procedures and triggers into 
> our database, which removes much of the logic from the developers 
> hands.  Creating an account is done the same way, whether you're using 
> our mobile front end, primary website, etc.
    The term "REST" is an early predictor for project failure a year or 
two down the road.  More than once I've been the guy who cleans up the 
mess after somebody ignorantly blunders into using "REST" for something 
that it's not appropriate for.

More information about the talk mailing list