Re: Net_FTP design issues
| From: | Paul M Jones | Date: | Thu, 14 Oct 2004 16:57:30 +0000 |
| Subject: | Re: Net_FTP design issues | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-33856@lists.php.net to get a copy of this message | ||
On Oct 14, 2004, at 11:48 AM, Tobias Schlitt wrote:
Hi Paul M Jones! On 10/14/2004 09:51 AM you wrote:That is a good idea and a worthy goal. :-) It sounds kind of PHP_Compat-ish ... would you think Net_FTP could be hooked into it somehow? -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: a collaborative online documentation system. http://yawiki.com/ Yawp: a single-file foundation for PHP applications. http://phpyawp.com/I would favor the OO approach, but that's just me. I'm afraid I don't understand the procedural argument; you could, for example, give the OO version static methods that can be called like plain functions (Net_FTP::connect() and so on). Then you have the best of both worlds.The benefit of a procedural version would be, that users who do not have (for whatever reason, eg. restrictive provider,....) the FTP ext, can just run scripts depending on it, as if it was there.