--------------Original Comment History----------------------------
Comment from = cf126330 on 2015-03-19 17:37:40 +0000
Several places in the spec contain the words "SkipListener" and "RetryListener", which may mislead readers to think there are so-named interfaces. It's better to use specific interface names like "SkipReadListener", "SkipProcessListener", "SkipWriteListener", etc.
"SkipListener" is used in section 11.8 Chunk with Listeners (except RetryListener) flow diagram.
These 2 old interfaces were broken down in
Bug 4303 - Break RetryListener down into multiple interfaces?
Originally opened as bug 6828 by cf126330
--------------Original Comment History---------------------------- Comment from = cf126330 on 2015-03-19 17:37:40 +0000
Several places in the spec contain the words "SkipListener" and "RetryListener", which may mislead readers to think there are so-named interfaces. It's better to use specific interface names like "SkipReadListener", "SkipProcessListener", "SkipWriteListener", etc.
"SkipListener" is used in section 11.8 Chunk with Listeners (except RetryListener) flow diagram.
These 2 old interfaces were broken down in Bug 4303 - Break RetryListener down into multiple interfaces?