On Fri, 27 Jul 2007, Alexandru Stanoi wrote: > 1. Which regexp to use for email validation? > > a. > > http://cvs.php.net/viewvc.cgi/pear/HTML_QuickForm/QuickForm/Rule/Email.php?revision=1.4&view=markup > b. http://iamcal.com/publish/articles/php/parsing_email/ > c. http://code.iamcal.com/php/rfc822/full_regexp.txt > d. http://ex-parrot.com/~pdw/Mail-RFC822-Address.html > e. http://www.tienhuis.nl/files/email_verify_source.php > f. This one (please specify): _________________ > g. Write our own one
a - that's what ext/filter uses and seem to be the most "logical" one. > 2. Do we need to support conversion to Puny code > (http://en.wikipedia.org/wiki/Puny_code)? > > a. NO WAY! > b. No > c. Not now > d. Yes > e. YES WAY! c - it's something for another addition. > 3. If the answer to question 2 was one of c, d or e, then where to put > the unicodeToPunyCode convert function (and the reverse function)? > > a. Mail > b. Url > c. Base > d. UserInput > e. a Tiein (please specify): _______________ > f. I can tell you where to put it! b - Url > 4. If the answer to question 2 was one of c, d, or e, how should the > unicodeToPunyCode function be triggered? > > a. Automatically everytime > b. Automatically if the email address contains characters outside of ASCII > c. Based on a function parameter, default false > d. Based on a class option, default false > e. Called manually by user > f. It should be hidden, with private and @ignore tags, and with an > obfuscated name, so that nobody will ever know it's there and nobody > will ever call it e > 5. How many functions which deal with email address validation should we > have? > > a. A function which does everything (regexp, mx, punycode) in one step, > with no possibility of changing the behaviour > b. A function in which the parameters say if the function should do mx > and punycode, which are not done by default > c. A function in which the class options say if the function should do > mx and punycode, which are not done by default > d. 3 functions, one for each step (regexp, mx, punycode). These will be > called independently > e. 4 functions (the 3 functions from d and the function from b) > f. 4 functions (the 3 functions from d and the function from c) > g. 7 functions (regexp, mx, punycode, regexp+mx, regexp+punycode, > mx+punycode, regexp+mx+punycode) h - a function that does regexp, and mx if an argument is passed; and an function that does punycode conversions (as a different addition later). Perhaps this is option b though, but the option was unclear. regards, Derick -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
