[Openicc] cupsICC on remote CUPS servers Part 2

edmund ronald edmundronald at gmail.com
Mon May 23 15:09:46 PDT 2011

Graeme, as ever you are right in principle; however maybe you could describe
a bit more how you would envision client and server to correspond, with an
emphasis on the fact that they may have been set up with different software
versions ...


On Tue, May 24, 2011 at 12:05 AM, Graeme Gill <graeme at argyllcms.com> wrote:

> edmund ronald wrote:
>> I see no reason why we should assume the print server knows about either
>> profiles or settings. The print server can be totally dumb, re. ink
>> settings
>> all I expect to hear from it is "Yes, Master, I do as Ye command!"
> I see very good reasons why the print server should know - they are
> device properties and the print server acts as the agent for the
> device to any (possibly remote) client using it.
> Yes you could hack up a way of placing this information somewhere
> else to work around a really dumb print driver/server, but you'd
> be better in that case to create server that is aware of
> printer settings and behaviour to encapsulate the dumb driver.
> Graeme Gill.
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20110524/0b0389d1/attachment.html>

More information about the openicc mailing list