Net_FTP design issues

Hi all! I recently got a new member for maintainance/development of Net_FTP. A friend of Helgi (CC'ed) started implementing the FTP functions provided by PHP using sockets and we will develop the new backend together. Now we're hanging at the decision of implementing the new backend in an OO or procedural manner. On the one hand I would preffer OO style, since all in PEAR is OO. On the other hand, if native FTP is not available one can simple include the code (if it's procedural) and will have the functions available with the same API. Forethat I'd preffer to have it procedural. What do you think? The procedural way would have another difficulty to ship around: Storage of the config stuff and Co., which would have been stored in the object in an OO way. I would suggest to store all of that in a global array (e.g. $_NET_FTP), which should not affect most of the scripts it would be used in. Opinion? Thanks in advance, regards, Toby -- Tobias Schlitt GPG Key: 0xA6529579 a passion for php http://www.schlitt.info Like to say "thank you"? - http://pear.php.net/wishlist.php/toby