Re: Re: cvs: php4 /ext/printer php_printer.h printer.c printer.dsp /win32 php_modules.dsw

On Fri, 27 Oct 2000, Daniel Beulshausen wrote: > > Do we really need to absorb every possible PHP module under > > well i think it's quite usefull, the way via com not very nice. > > > the sun? This looks like the ideal candidate for getting > > distributed separately. > > are you pointing to that it's available not on *nix? > we have alot of extensions, which are not available for windows in the cvs > as well, aspell, ccvs, posix, yp, swf,... I'd say that the main point is that PHP was, originally, a language geared to make web development easy. And that is still its main use, although the language seems to have reached in some peoples use also the status of main system scripting language. Interfacing with printers on a server running services that can be seen and used by uncontrollable outside world could be a bit questionable, if PHP is still seen as a language of its original purpose. And a very possible hole for a kind of DOS. But, thinking about controllable intranets, it could be an extremely good feature. Hmm. Don't know even myself what my exact opinion is. Every possibility has both its good and bad sides. Personally, I'd too say that this is an extension that should be distributed separatedly. Now, having said that, and being quite vague about where I stand in general related to PHP, if this extension will remain in the main distribution, could I ask you to rename it to 'win-printer'? There must be room for the options --with-win-printer, --with-kde-printer, --with-gnome-printer, or I must ask you yourself to write that config.m4 that handles --with-printer[=[shared,][gnome|kde|win][,directory]]. -- Jouni Ahto