Subject: Re: [boost] Mutexes claim a Windows event handle
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-06-03 08:45:08
----- Original Message -----
From: "Peters, Richard" <richard.peters_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, June 03, 2010 1:50 PM
Subject: Re: [boost] Mutexes claim a Windows event handle
> I'll explain our architecture at a high level, and see if we can come up
> with a better way of locking.
>
> Those 100.000 'objects' are in fact print jobs in a print controller.
> Each job contains the structure describing what the job looks like
> (sheets and pages and such, among with their attributes like stapling or
> how the bitmaps should be rotated), stuff for maintaining progress and
> accounting, a pipeline of objects doing all sorts of manipulations like
> making it a duplex job or creating booklets of it, etc. A job is
> constructed by either ripping a document (for instance postscript) or by
> scanning a document. This ripping or scanning is kind of repeated after
> a user edited the job on the user interface. All the while, the printer
> wants to get information from the job, in order to be able to print the
> job while it's still ripping.
Do you confirm that you want to have up to 100.000 printer jobs concurrently?
Best,
Vicente