Re: ATL singleton

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Fri, 19 Sep 2008 08:31:21 -0400

Message-ID:

<egtCiOlGJHA.2232@TK2MSFTNGP04.phx.gbl>

"Alexander Lamaison" <newsgroups@lammy.co.uk> wrote in message
news:u2BBxKlGJHA.3928@TK2MSFTNGP03.phx.gbl

I'm working on my namespace extension
(http://swish.sourceforge.net/) and I'm trying to pass data between
IShellFolder instances. This data is the current 'connection' to a
remote server (a COM object). The idea is to prevent users having
to retype their password every time they navigate to a subfolder,
for instance.

Probably the easiest thing to do would be to stick that remote
server's pointer into the ROT (see IRunningObjectTable) under some
agreed-upon name (item monikers are handy for that). Then any folder
instance would be able to pull it out.

Thanks Igor! I've never heard of the ROT before and don't really
understand Monikers but from a scan of MSDN this sound like it might
be what I want.

For your scenario, you may think of an item moniker as just a fancy
wrapper around a string. You create one with CreateItemMoniker, and you
call IRunningObjectTable::Register to register your connection interface
under that string.

I'm still a bit confused about how the IShellFolder
instances will get access to the connections.

IRunningObjectTable::GetObject, of course. You create another item
moniker using the same string.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925