Wullie,
It
is a flaw in the article -- a flaw in premise. To paraphrase, the article suggests that using mailto: won't work because of a variety of reasons. Its example is a business that is doing ordering online.
The second paragraph sets the premise that the intended audience of this article is basically "everyone in the world" who feels like publishing online.
The third paragraph addresses the submitting of orders for a business, which is
not the typical or common use of the supposed intended audience.
So, either the article is suggesting that
everyone use server-side forms and avoid the mailto: link (with which, frankly, I disagree) or it is flawed in its premise of audience (who running a business online where they're taking orders would be so stupid as to use a mailto: link? Wait -- I've seen 'em, I guess).
So that's the flaw.
There is absolutely nothing wrong with using server-side e-mail apps. Some people don't have that knowledge or they don't have the interest or they just want a little link put up, nothing fancy, to send casual e-mail.
Now, an issue I
didn't mention before but will since I've learned more, is that the article above is not "informative" so much as a pseudo-informative fear-based ('...you don't want to lose Valuable Customer Data, do you?!') shill for what seems to be a spam-mailer. Yeah, it sends your form contents, but it also sends ads at the header and footer of each letter. Feh.
My business would do better
without an uncontrolled ad-insertion in my e-mail and thank-you pages. Yucko.
Cian has an excellent point in that pretty much anyone who
wants server-side CGI capability can afford it. I just priced out some hosting solutions and found some very cheap ones that are cheap because they
don't support a bunch of Microsoft server-side stuff -- but they do include Perl!
Cheers,
![[monkey] [monkey] [monkey]](/data/assets/smilies/monkey.gif)
Edward
"Cut a hole in the door. Hang a flap. Criminy, why didn't I think of this earlier?!" -- inventor of the cat door