[cups.development] Backend for Canon network protocol
mike at easysw.com
Fri May 9 18:37:10 PDT 2008
Louis Lagendijk wrote:
> On Mon, 2008-05-05 at 08:54 -0700, Michael R Sweet wrote:
>> Louis Lagendijk wrote:
>>> I have made the code I developed so far available on
>>> Modifications can be found in runloop.c and bjnp.c which is for now a
>>> copy of socket.c with small modifications. This code is just a
>>> See all the udp command stuff in bjnp-io.c for all the canon specific
>> OK, given that you need to send commands out-of-band, a port monitor
>> won't help.
>> Also, because of the nature of the changes, I don't see
>> us incorporating them into the socket backend, but we'll be happen
>> to host a link on the CUPS links page:
> What exactly are you objecting to that makes it undesirable to merge
> this into socket.c? Is it the usage of the write call in runloop? Other
> changes can easily be cleaned up. It is not that I object, but I would
> like to uderstand....
The issue is mainly the amount of extra code for something that
will not likely apply to any other vendor's devices...
> And thanks for the offer of hosting a link. When I am ready, I will
> definately take up the offer
> Thanks for your help and great product!
> kind regards, Louis
Michael Sweet, Easy Software Products mike at easysw dot com
More information about the cups