Times when LogBook can screw you up

[Kevin Fitzpatrick]

I recently came across a time when using LogBook can screw things up
for you.

I've been using LB to output traces from a legacy AS2 project. It's
great since it works over LocalConnection so it's AVM version agnostic.

I encountered a problem because this particular piece of code relied
on LocalConnection to talk between a few of it's components and it
also was doing a ton of rapid succession logging. The LocalConnection
ended up getting flooded with messages and was causing the main
application's LC messages to respond very slowly. They were waiting
for the logging LC messages to get out of the way.

In a conversation we recently had, Arpit mentioned that he had heard
of some classes which will wrangle your LC messages. Perhaps we can
put some of that wrangling into LB to prevent situations like this.

At the end of the day, LocalConnection is single threaded and it can
deal with messages only so quickly.

Does anyone else have any input into this problem?

Thanks,
Kevin