Dominic Cleal wrote:
I agree that it adds another layer of complexity, but
I don't agree that
there's no easy way to provide "debug info". I think you're in exactly
same boat whether you use HTTP or SMTP for an interface if your network or
SMS provider fails. Most MTAs have extensive logging if there is a need to
debug -- they're pretty tried and tested.
Actually SMTP would be more complex, most smtp apps would dump the
message into the local MTA and you'd have to hope it was running, where
as doing HTTP, and this is where the perceived level of complexity
increases, you do the connection directly from your app or what not.
Running an MTA (rather than ssmtp etc) means you will
have queueing and
message retries provided in case your SMS provider falls over. It's also
easy to test and switch providers if necessary with little change.
Exactly! :) It also means the level of complexity goes up with it.
- Enterprise Two Factor Authentication
- Think globally, network locally
- Telecommunications Freedom
- Global Communication for the 21st Century
"In the long run the pessimist may be proved right,
but the optimist has a better time on the trip."