Folks;

We need a way for various programs external to Perforce to know when a file has been submitted to a particular portion of the depot.

Polling won't work, too much overhead *and* too much latency, we need sub-second response times for certain of these events. Counters won't work because they're a slightly augmented version of polling :)

So our goal is to have a 'reader' which slurps up the journal file as it's produced, looking for certain events.

It LOOKS to me like the sequence to search for is the following:

@rv@ 1 @db.locks@ @//depot/foo.txt@ @cpatti-all-racer@ @cpatti@ 0 1 @rv@ 0 @db.change@ 1 1 @cpatti-all-racer@ @cpatti@ 1001358507 1 @Trying to track journal activit@

Does this make sense to people? Are there any other instances where such a sequence might come up?

I realize Perforce can't support this kind of thing, but we need more than the product delivers and hoping really hard that post submit triggers will become a part of the standard distro isn't an option given our timeframes here.

Thanks!

-Chris