On 11/29/2017 01:43 PM, Paul Sandoz wrote:
SubmissionPublisher --
1004 // Order-sensitive field declarations
Is this still relevant
Not really; layout is now discussed in class-level doc. Removed. Thanks.
81 * <p>A single SubmissionPublisher may be shared among multiple 82 * sources. Actions in a source thread prior to publishing an item or 83 * issuing a signal <a href="package-summary.html#MemoryVisibility"> 84 * <i>happen-before</i></a> actions subsequent to the corresponding 85 * access by each subscriber. But reported estimates of lag and demand 86 * are designed for use in monitoring, not for synchronization 87 * control, and may reflect stale or inaccurate views of progress.
We probably need a CSR for this.
Yeah, I guess so, even though it is just a clarification.
Is “corresponding access by each subscriber” referring to access of the published item by each subscriber?
Yes. And also for signals like closeExceptionally exceptions. This seems to cover both cases, but maybe could be improved. -Doug