Not entirely! In fact, this was a very good aspect of my monitor in that no
matter what threads were doing the monitor produced output in a synchronized
manner because I used a critical section.

There's always more than one way to skin a cat. But, as it seems so far in
life, there's never a perfect way.

Jason

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Martijn Tonies
> Sent: Thursday, December 15, 2005 12:25 AM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] IBO with pure Firebird environments
>
>
>
> > J> What I would like to be able to do is have a
> > J> TIB_Session that has its own client dll so that you can
> have more than
> one
> > J> in the app and thus have a Firebird session and an
> InterBase session in
> the
> > J> same application. The problem I'm having getting there
> is I currently
> rely
> > J> on some global settings for my trace monitor.
> >
> > I think your only way out is to require IB_Monitor to be hooked to a
> > specific IB_Session instance (and having it find the
> default one like
> > the other components do). Not backward compatible, but coherent.
>
> That would defeat the purpose of the monitor.
>
> Why not have a single pass-through for all sessions? Instead
> of re-routing
> DLL calls, let the monitor hook themselves into available sessions?
>
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL,
> Oracle & MS SQL
> Server
> Upscene Productions
> http://www.upscene.com
> Database development questions? Check the forum!
> http://www.databasedevelopmentforum.com