The architecture where "multiple processes communicate with a shared
database" gets less credit than it deserves. In your case I think there's
no reason you can't write your batch scripts in PHP: pretty commonly I
write command line scripts that run as cron jobs... In that situation,
you
On Mon, Jan 4, 2010 at 2:57 PM, Matt Juszczak wrote:
>> 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 appropr
Paul A Houle wrote:
Matt Juszczak wrote:
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.
Well, w
Matt Juszczak wrote:
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.
Well, we didn't go that rout
Yeah, that's how I was looking at it and since I'm the only one other
than QA and coders that will be there, I'm not concerned or interested
in having anyone look bad. Nothing more frustrating than getting into
a religious argument when there's essentially nothing wrong. Just a
different way
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.
Well, we didn't go that route. We had three choic
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 ov
Hi John,
It really sounds like you really have your mind set on building a
fancy pants queue system, but cant really justify it. Frankly, I
think you are doing some technical masturbation, want to build
something far more complicated than is actually needed, and want to
solve problems that don'
On Sun, Jan 3, 2010 at 4:24 PM, wrote:
> Hi all,
>
> I'm working on a website right now and am in charge of implementing email
> functionality.
What does that mean? What specifically are you in charge of
implementing. Are you going to build and maintain an Emailor api that
other developers wi
Matt Juszczak wrote:
So really, this is a case of figuring out how to standardize email
generation, not necesarilly sending.
It's definitely nice to be able to push a "STOP" button on putting
messages into your MTA, both for operational issues, but also when you
find out [just after st
On Wed, Dec 30, 2009 at 11:18 AM, Tom Melendez wrote:
>
> 2. You find something wrong, then what? And what if it is not
> "really" wrong (Jones uses a selection sort but sould have used an
> insertion sort, and no one told him beforehand). Do we hold up the
> project until the engs figure out w
Paul,
I'm actually pretty confident I can keep the mail servers running
efficiently - it was actually my primary task at my previous job.
Removing the MTA out of the picture entirely, I'm simply trying to decide
how to push messages into the mail queues on the mail server themselves.
I've alr
Matt Juszczak wrote:
Paul,
Sure, but I'd also send "high priority" and "low priority" emails
through separate systems (sendmail/postfix/whatever instances.)
Well, what's to stop me from using the same database table for high
priority and low priority, but having the high priority backgroun
Ben, David, Tom,
Thanks for the insightful input.. Sorry for the delay in responding,
but was gone over the holidays.
My take away is that they can be useful if applied in a manner that
avoids "pissing contests" between specific approaches, driven from above
with specific objective(
On Sun, Jan 3, 2010 at 7:03 PM, Hans Zaunere wrote:
> Saw this one, too - somehow my control panel doesn't look like this guy's.
> But, as far as I can tell, the FastCGI timeout is set to 600 seconds, which
> is far greater than the roughly 60 second timeout I'm seeing. Now I
> wouldn't bet the
Paul,
Sure, but I'd also send "high priority" and "low priority" emails through
separate systems (sendmail/postfix/whatever instances.)
Well, what's to stop me from using the same database table for high
priority and low priority, but having the high priority background process
continuousl
Matt Juszczak wrote:
So how about this:
For things like password recovery, private message notifications,
welcome emails, etc. that are initiated by the user and are only sent
to one user, I'll do those in the code base (the negative being I have
to code that twice, in both front ends).
Fo
On Mon, Jan 4, 2010 at 10:37 AM, Matt Juszczak wrote:
>
> Would it really be so bad to do the following for say, a forgot password
> attempt:
>
> - Someone hits "Forgot password" on the site
> - Our front ends calls a stored procedure inside the DB that generates a
> hash, adds a pending email to
Matt Juszczak wrote:
store everything in a db. don't be too fussy about the design. you're
just crunching emails.
That's the thing. I do want to store everything in the DB! Since we
have so many front ends, I'd much rather control all the emailing with
triggers and stored procedures (and a
store everything in a db. don't be too fussy about the design. you're just
crunching emails.
That's the thing. I do want to store everything in the DB! Since we have
so many front ends, I'd much rather control all the emailing with triggers
and stored procedures (and a background running pr
On 1/4/2010 10:02 AM, Justin Dearing wrote:
For talking to MS SQL server, as Hans is, (which IMHO is superior to
MySQL and Postgres for performance, but not postgres for features) it
makes sense to use windows. While apache runs on windows easy enough,
IIS "just works" on windows.
Well, my exp
On Mon, Jan 4, 2010 at 9:50 AM, Gary Mort wrote:
>
>
> Also check out LogParser,
> http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=enit's
> a great tool for querying the event log like a database and getting
> more reasonable data out of
For talking to MS SQL server, as Hans is, (which IMHO is superior to MySQL
and Postgres for performance, but not postgres for features) it makes sense
to use windows. While apache runs on windows easy enough, IIS "just works"
on windows.
On Mon, Jan 4, 2010 at 9:40 AM, Jake McGraw wrote:
> On
On Sun, Jan 3, 2010 at 5:41 PM, Hans Zaunere wrote:
> Oh my :)
>
> I'm developing an application running under IIS 7 using FastCGI and PHP
> 5.3.
> I've used the recommended installation procedures from MSFT for getting
> things setup using their Web Platform installer.
>
> 1. When I call trigge
On Mon, Jan 4, 2010 at 9:05 AM, Justin Dearing wrote:
> On Mon, Jan 4, 2010 at 7:17 AM, David Krings wrote:
>>>
>>> Just being curious and sorry for digressing, but which requirements would
>>> that be? Running commodity tasks on the most expensive server OS with the
>>> worst web server availabl
On Mon, Jan 4, 2010 at 7:17 AM, David Krings wrote:
> Just being curious and sorry for digressing, but which requirements would
>> that be? Running commodity tasks on the most expensive server OS with the
>> worst web server available?
>
>
> With an attitude like that, businesses must be busting
> >>> Oh my :)
> >>
> >> That applies to IIS, right? I just have to ask the question: can't you
just
> >> use a real web server that actually works, like, let's say, Apache? I
'work'
> >> with IIS at work and it is a totally dysfunctional kludge.
> >
> > We're actually porting away from Apache to m
On 1/3/2010 7:03 PM, Hans Zaunere wrote:
Oh my :)
That applies to IIS, right? I just have to ask the question: can't you
just
use a real web server that actually works, like, let's say, Apache? I
'work'
with IIS at work and it is a totally dysfunctional kludge.
We're actually porting away
28 matches
Mail list logo
