On Fri, 2012-03-09 at 08:21 -0900, Jef Spaleta wrote:
> Back to the use case of a primarily single user laptop touching
> multiple networks on a daily basis. For that situation is it expected
> that the default print server will still be the laptop's own cup
> server for networked printers?
Netwo
On Fri, Mar 9, 2012 at 12:46 AM, Tim Waugh wrote:
> Yes, exactly, and that is what I'm suggesting. For printing entirely in
> the user session it is a case of using an alternative to using CUPS
> running on the local machine, so that means:
>
> a) no filters or drivers; the job document is the PD
On Thu, 2012-03-08 at 09:52 -0900, Jef Spaleta wrote:
> 2012/3/8 Miloslav Trmač :
> > The lazy answer to both is "fail, or not, the same way as cups
> > currently fails, or not" (in fact, could the session printing service
> > simply be cups that treats the system instance as another remote
> > ser
2012/3/8 Miloslav Trmač :
> Right... I just wanted to make sure that any potential work on user
> session printing is not discouraged by adding requirements that are
> not currently satisfied with the system daemon.
Of course. That wasn't meant as stop energy. If those situations
nce as another remote
>> server?).
>
> If we were looking for the lazy answer, we'd just not bother with queing at
> all.
Right... I just wanted to make sure that any potential work on user
session printing is not discouraged by adding requirements that are
not currently sa
2012/3/8 Miloslav Trmač :
> The lazy answer to both is "fail, or not, the same way as cups
> currently fails, or not" (in fact, could the session printing service
> simply be cups that treats the system instance as another remote
> server?).
If we were looking for the lazy answer, we'd just not bo
On Thu, Mar 8, 2012 at 7:19 PM, Jef Spaleta wrote:
> 1) What if I've hopped networks since then and the print job that was
> que'd was on a printer that was only visible on the original network?
>
> 2) What if I've hopped networks and the old network and the new
> network have a printer at the sam
On Mon, Mar 5, 2012 at 8:02 AM, Bill Nottingham wrote:
> Tim Waugh (twa...@redhat.com) said:
>> For a plain network printer, where the printer might not be able to
>> accept the job while it's busy processing others, you might have to
>> queue the job and retry it later. So if you are doing that
On Mon, 2012-03-05 at 12:02 -0500, Bill Nottingham wrote:
> Tim Waugh (twa...@redhat.com) said:
> > For things like cloud printing, where the print server is a hosted
> > service somewhere out in the Internet, I think the applications should
> > be talking directly to it (via the print dialog).
>
Can't we just get the policy right so that users can add queues?
Tim.
*/
signature.asc
Description: This is a digitally signed message part
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Le Mar 6 mars 2012 14:53, Miloslav Trmač a écrit :
> This requires:
> * A network printer
> * ... that has a 300page paper tray, so it is clearly an industrial one
̌1. The standard paper tray for even the smallest laser is usually 250 pages,
they are dirt cheap and a second paper tray is not exp
On Tue, Mar 6, 2012 at 2:46 PM, Nils Philippsen wrote:
> On Mon, 2012-03-05 at 12:02 -0500, Bill Nottingham wrote:
>> Tim Waugh (twa...@redhat.com) said:
>> > For things like cloud printing, where the print server is a hosted
>> > service somewhere out in the Internet, I think the applications sho
On Mon, 2012-03-05 at 12:02 -0500, Bill Nottingham wrote:
> Tim Waugh (twa...@redhat.com) said:
> > For things like cloud printing, where the print server is a hosted
> > service somewhere out in the Internet, I think the applications should
> > be talking directly to it (via the print dialog).
>
Tim Waugh (twa...@redhat.com) said:
> For things like cloud printing, where the print server is a hosted
> service somewhere out in the Internet, I think the applications should
> be talking directly to it (via the print dialog).
>
> For a plain network printer, where the printer might not be abl
(changing the subject line since this is a bit different from the
original topic)
On Sun, 2012-03-04 at 00:22 +0100, Miloslav Trmač wrote:
> Another way to look at this issue is - if printers were maintained
> per-user (per-user, unprivileged cups daemon, per-user configuration,
> per-user print q
15 matches
Mail list logo
