<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Edmund,<div><br><div><div>On 2013-05-22, at 11:55 AM, edmund ronald <<a href="mailto:edmundronald@gmail.com">edmundronald@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr">Is the idea bad because it would place additional burden on the CUPS maintainers, or is it bad for some architectural reason? </div></blockquote><div><br></div>It is bad from a security, a maintenance, and a forward-looking-architecture perspective.</div><div><br></div><div>Consider that we'd need to provide proper access controls, limits (don't want to use up all memory/disk with this data store), methods for enumerating resources that are available and a way to delete old resources (probably some of the WebDAV methods, none of which are currently supported by the CUPS HTTP stack), and all of the supporting security checks to make sure you aren't trying to store data someplace you are not supposed to.</div><div><br></div><div>And then are the resources per-printer, per-server, per-user? Not a simple thing to add or maintain, all for just one project that wants it (Gutenprint) to support printer drivers that we are trying to eliminate (the future is IPP Everywhere).</div><div><br></div><div>A more likely future solution is that Gutenprint will become its own IPP Everywhere service (something that future CUPS will provide a framework for, so this isn't as big a deal as you might think), and at that point you can add whatever resource management solution you like, internal to Gutenprint.</div><div><br></div><div><blockquote type="cite"><div dir="ltr"><div>My reasoning is that if data cannot be passed via the options (too big) then it needs to be put in a file somewhere, if PPDs are going away then the PPD file is a bad place, and another file means a security headache etc, so why not squirrel the stuff away via CUPS.</div></div></blockquote><div><br></div><div>Because you aren't getting rid of the security headache, you are making it incredibly larger by having a network-accessible server manager it, particularly one that does not support the HTTP methods needed to implement such an architecture.</div><div><br></div></div><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span> </div> <br></div></body></html>