Re: A New Quirk - Filter Pools

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

I must have been having a Monday on a Tuesday, Brian.

The problem arose when I tried to open a filter in a brand new connection.
Rather than prompting me for the new connection, WDSC prompted me for the
default connection (the first connection I had ever created in the
workspace).  That started me down the rabbit hole, the end of which was
finding the strange "MACHINENAME filter for CONNECTIONNAME."  And while that
is still the case, I can't get the original behavior to reoccur.  When I
open a filter, the correct connection is opened.

How odd.  Again, I'll just chalk it up to Monday on a Tuesday and see if it
happens again.

Joe


> From: Brian Parkins
>
> > > However, when you create a filter pool, it is by definition shared among
> all
> > > your connections.
>
> That has not been my experience, Joe.  (I just tried it out again and
> checked with the Help topic.)
>
> My understanding is that Filter Pools are private to the Connection.
> Filters created within such (private) Filter Pools can only be used in
> that particular Connection.  (Aside: Filters are "owned" by the Profile -
> not the Connection.)
>
> Filter Pools CAN be shared across different Connections through a Filter
> Pool Reference.
>
> The default Filter Pool, (which has the same name as the Profile) _is_
> shared across Connections.  As such, it is an example of a Filter Pool
> Reference.
>
> The concepts of Profiles, Connections, Filter Pools, etc. can appear
> confusing and overly complicated.  (Took me a while to wrap my brain
> around them.)   For this reason I believe the option of making a Filter
> shared or private across Connections was added to WDSc, (at Version 6?) to
> allow for a simpler setup.
>
> Brian Parkins