[cups-devel] Create-Job-Subscription seems not Implemented in cups1.7
Nicolas
nicolas.delaby at ezeep.com
Fri Mar 14 08:04:08 PDT 2014
On 03/14/2014 01:30 PM, Michael Sweet wrote:
> Nicolas,
>
> Both operations are supported and perform similar functions - the
> implementation in cupsd adapts to its input.
>
> What issues are you seeing?
>
Hi Michael,
Assuming there is a job existing with job-id = 7
I run ipptool command with the following file
{
NAME "Create Job Subscription"
OPERATION "Create-Job-Subscription"
GROUP operation-attributes-tag
ATTR charset attributes-charset utf-8
ATTR language attributes-natural-language en
ATTR uri job-uri ipp://cups:631/jobs/7
ATTR name requesting-user-name admin
GROUP subscription-attributes-tag
ATTR uri notify-recipient-uri rss://
ATTR keyword notify-events all
}
cups complain the job_uri is not valid (I guess)
==> /srv/docker/cups/var/log/cups/error_log <==
D [14/Mar/2014:14:55:35 +0000] [Client 9] 1.1 Create-Job-Subscription 51925
D [14/Mar/2014:14:55:35 +0000] Create-Job-Subscription
ipp://cups.dev.ezeep.net:631/jobs/7
D [14/Mar/2014:14:55:35 +0000]
cupsdCreateSubscription(con=0x7fcd6b00c960(9),
uri="ipp://cups:631/jobs/7")
D [14/Mar/2014:14:55:35 +0000] Create-Job-Subscription
client-error-not-found: The printer or class does not exist.
If I ran the Create-Job-Subscription operation with printer-uri and
job-id, then it returns 'successful-ok' but it creates another yet
Printer Subscription.
Once the job is performed, the Subscription is still there, as I
understood the spec, the duration life of Job Subscription is bound to
the life of the job it monitors.
This is why I concluded that Create-Job-Subscrption does the same thing
as Create-Printer-Subscription.
Best,
Nicolas
--
Nicolas Delaby · Software Engineer · ezeep.com
ezeep GmbH · Ohlauer Str. 43 · 10999 Berlin · Germany
Registry Court: Charlottenburg · HRB133318 · Managing partner: Sascha
Kellert
More information about the cups-devel
mailing list