[cups.general] Concurrent IPP transfers and other CUPS operations

[Tim Waugh]

Helge Blischke wrote:
>> Suppose you had a slow IPP transfer from a remote site, and another
>> transfer was ready to start (perhaps to a different queue) - will the
>> second transfer have to wait for the first to finish?
>>
>> Thanks in advance!
>>
>> Seb James
> 
> No, for every job, the scheduler spawns a process group of its own
> which contains all the needed filters and the backend.

That wasn't actually the question, which was about the network handling 
of IPP requests.

In fact there are several situations in which handling one IPP request 
blocks the scheduler for potentially large amounts of time, preventing 
it from servicing both jobs and other IPP requests.  One such situation 
is when fetching lists of jobs, for example:
   http://cups.org/str.php?L2913

Ideally, IMHO, this would be handled using the 'worker threads' 
paradigm, but unfortunately that's not the way cups works.

Tim.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
URL: <https://lists.cups.org/pipermail/cups/attachments/20090406/895d45eb/attachment.bin>