Marty Joel wrote:
> ...
> MS> Yes, this should be the expected behavior, with the subscription
> and job disappearing only after all events have expired.
>> <MJ> The subscription object must persist, not necessarily the job
> object. An implementation could store per-job subscription
> objects that are not linked to job objects, and which are
> deleted at their expiration time, even if the job object has
> already been deleted because its job retention and job history
> phases have elapsed.
This prevents you from gathering the job-media-sheets-completed
attribute after a notification that a job is complete, for example.
I *thought* that we wanted a client to be able to query a job object
after receiving a notification, and that job object should only
disappear after all events referencing the job object expire.
> ...
> <MJ> Chinking isn't required for multipart, and I wonder if they
> are even compatible.
They are, but of course you'll need HTTP software that knows how
to do it right (with the embedded content headers chunked like the
rest of the data...
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com