Re: Re: Net_FTP design issues

> >> However I think it could become PHP_Combat_FTP or something as a > >> separate package (especially since it adds a dep on the socket ext?) > > > > Why should this add a dependency on ext/sockets? > > I think this will require a call to fsockopen() as only client > > functionality is needed. > > k .. i wasnt sure :-) > > anyways I still think it should be separate .. how many functions are we > talking here? php.net/ftp lists 34 ftp functions + 10 constants. Currently there are ready drafts to 15 functions using sockets. > > I would say if its more than 5 functions we should make it a separate > package. Even then I think it would be a good example to set putting > entire ext emulations into their own PHP_Compat_Foo package instead of > quickly bloating PHP_Combat into an insane size by future similar solutions. What about Michael´s idea? "Create new category for PHP code redefining whole PHP extensions" - Hannes