public interface IFilterCallback
The callbacks occur during critical sections of the underlying RPC protocol handlers and that callback implementers should ensure that the callback methods return as quickly as possible and that they do not themselves call back into the server layer.
If any of the callback methods throw a P4JavaException the system will rethrow the same exception from the main streaming command method after attempting to clean up; similarly with P4JavaErrors. In either case, while the main method has returned and no more results are available, the state of the underlying protocol layers is not defined, and you should proceed carefully from that point on (in the case of 'ordinary' P4JavaExceptions, the underlying state is actually typically stable and OK for continuing on, with a possible delay due to non-terminated results still being sent to the API; however, all bets are off with the P4JavaError case).
| Modifier and Type | Method and Description |
|---|---|
java.util.Map<java.lang.String,java.lang.String> |
getDoNotSkipKeysMap()
Per every RCP packet received from the Perforce server, callback to the
consumer to get a map of do-not-skip keys for informing the RPC layer not
to skip them.
|
void |
reset()
Per every RCP packet received from the Perforce server, callback to the
consumer to reset any counters and other variables.
|
boolean |
skip(java.lang.String key,
java.lang.Object value,
java.util.concurrent.atomic.AtomicBoolean skipSubsequent)
When called, this method signals to the consumer that an individual
key/value pair is being processed for the current received RPC packet
from the Perforce server.
|
void reset()
throws P4JavaException
P4JavaException - if any problem that should stop normal command processing.boolean skip(java.lang.String key,
java.lang.Object value,
java.util.concurrent.atomic.AtomicBoolean skipSubsequent)
throws P4JavaException
Consumers are assumed to be able to make sense of the key/value pair quickly and on their own -- no help is (currently...) given to consumers with this.
NOTE: this method is called in a critical section of the underlying P4Java client / server protocol handler, and must not cause any undue delays or calls back into the server. Serious protocol-level errors and / or major performance problems can result from even minor implementation errors with this method (and these problems can be extremely difficult to debug), so you are on your own if you use this feature.
key - possibly-null key (string) part of the key/value pair.value - possibly-null value (object) part of the key/value pair.skipSubsequent - reference parameter passed-in from the RPC layer.
Set this to true if the callback wants to skip subsequent
key/value pairs for the rest of the current received RPC packet.
Note that some RPC protocol related key/value pairs (i.e.
'func', etc.) are not skipped.P4JavaException - if any problem that should stop normal command processing.java.util.Map<java.lang.String,java.lang.String> getDoNotSkipKeysMap()
throws P4JavaException
Only the map keys are used for lookups; the map values are not used. This is normally used coincide with the 'skipSubsequent' callback reference parameter set to true in the 'skip()' method.
NOTE: since this method is called frequently, the do-not-skip keys map should probably be constructed once and outside of this method. Maybe a good place to build this map is in a constructor or an initialization method.
P4JavaException - if any problem that should stop normal command processing.