I would agree that the CUPS API floats among several categories. The reason why Net seems like the most appropriate place for such a module is that:
1) Net::LPR is already a registered module and Net::CUPS is very similar to that in that it provides the same functionality, but is restricted to the CUPS software package. 2) Eventually I would like to reveal the IPP C API of cups with this module - it just isn't on the todo list for next week. 3) The difference between working with a remote CUPS sever and a local one is nill with the C API. Communication is done the same way. Any suggestions for a more appropriate namespace is definately appreciated. On Mon, 24 Mar 2003, A. Bergman wrote: > > On måndag, mar 24, 2003, at 04:24 Europe/Stockholm, Perl Authors Upload > Server wrote: > > > > > This is just an interface to the C API of CUPS. It has the basic > > functionality of printing and job control implemented. I may in the > > future expose the Internet Printing Protocol (IPP) API of CUPS as > > well as the PPD functions. In theory, this module could allow for > > more "intelligent" printing for perl applications. > > > > > > I am not so sure Net::* is the correct place for an CUPS api (even if > that is a nice thing) bridge, if it was a Net::IPP makes sense but CUPS > is not only Net related. > > Arthur > -- //========================================================\\ || D. Hageman <[EMAIL PROTECTED]> || \\========================================================//
