--nextPart2838038.B0nTja2Zgb
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 15 September 2007, Kurt Pfeifle wrote:

>  Disadvantages:
>   - the PDF generating backend needs to run as root in order to be
>     able to write resulting files into a user-private directory

It could just use a little suid helper.
However, if such a CUPS option would be available, I would expect it to=20
transfer the generated data via socket/IPP to the client.
This would even make it work with a remote CUPS server.

>   - needs CUPS in the first place, needs a *working* CUPS, and
>     needs cupsd running

Given the rise of Unix on the desktop (including proprietary like Mac OS X)=
,=20
it IMHO makes perfect sense to delegete jobs to shared infrastructure inste=
ad=20
of providing it ourselves.
There are enough places where this shared infrastructure does either not=20
exists yet or is not good enough for our needs so we have to do it ourselve=
s.

> I have to add now to the disadvantage side:
>   - doesn't work with KDE KIO

If the file is available to the client which requested it, it can always do=
=20
the KIO transfer after the "printing".
AFAIK no difference to the KDE3 PDF creation chain, or does it output to th=
e=20
KIO location directly?

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart2838038.B0nTja2Zgb
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBG6/mcnKMhG6pzZJIRAqCoAJwP2r8qbc+y0xnGJ/UQ5m22nVkJzwCfZVur
WRm2zGqdXiPTcc35dQFlLyQ=
=W+QJ
-----END PGP SIGNATURE-----

--nextPart2838038.B0nTja2Zgb--