[email protected] wrote:
Folks,
This is the code review for 11854, which places a lock around the
external interfaces to the transport.  Callers that call transport
methods will now find themselves serialized against this lock.  This
should prevent multi-threaded applications that are unable to manage
their own calls into the transport from crashing because two threads
simultaneously try to call the engine's run (perform) method.

        http://cr.opensolaris.org/~johansen/webrev-11854
Just to confirm my understanding, a Transport object is created for each Image object, so if one has two Image (or ImageInterface) objects for different images, then concurrency between those objects is still allowed, right?

Also, if there are two Image (or ImageInterface) objects created for the same image (using the same path) from two different threads in the same process, then those can proceed in parallel. This would probably cause meta-data problems, but that is not the responsibility of the transport to fix, i.e., that is a different wad (bug 1668). Right?

Thanks.
Tom

<<attachment: Tom_Mueller.vcf>>

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to