On Wed, Mar 14, 2018 at 11:11:23AM +0000, Arnt Gulbrandsen wrote:

[cut]

>
> Some things not mentioned today: Problems because rendering whole pages to
> bitmaps on the client needs so much RAM that the UI grows unresponsive,
> other problems if the client renders the pages in sequence to save RAM and
> the user closes the laptop once the first page starts printing, yet other
> problems if the printer runs out of RAM while rendering the current page
> because it's allocated too much RAM to buffering giant subsequent pages, yet
> other problems if the printer driver avoids using bitmaps and the printer
> firmware misrenders an embedded font.
>
> It's $%@#$!@#$!@# annoying when people come afterwards and explain how
> simple a task is, and clearly have no idea about the complexities and
> problems.
>
> Maybe d-bus is a poor fit for hplip. I don't know and I suspect you don't
> either.
>

My poor understanding of the matter is that the dbus dependency is
necessary mainly to let fancy GUI applications talk to hplip, and to
obey "session-related" policies, not for hplip to do anything in
particular with the print job. And I could not imagine hplip needing
dbus to do anything at all with a job to be sent over the network
(i.e., not to the USB printer attached to the same host that talked to
hplip).

My2Cents

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[     "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[       @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[     @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]