>      Sam>  Multiple calls will be fine (although I'm confused why an app
>      Sam>  would need to request multiple identities simultaneously)
>
> When my pidgin starts up I log into about 5 chat services.
> I only have one mail account on my desktop, but I know a lot of people
> who have several.

That makes sense, not sure why I didn't think of this :)

>      >>  IN response to the MSVC support.  You need to produce an msvc compatible
>      >>  import library.  Your library needs to have an ABI that can be called
>      >>  from MSVC. (I think that means no C++ in your exposed ABI). Your public
>      >>  header file needs to be something that can be included from MSVC.
>      >>
>      >>  I don't think it is a requirement that your dll be buildable with MSVC,
>      >>  particularly if you build it as part of the existing moonshot-ui package
>      >>  which already requires mingw.  I don't think libtool in mingw mode
>      >>  produces import libraries, but I believe it's fairly easy to produce
>      >>  them from what it does build.
>
>      Sam>  Great, this is the easiest option. MSVC is required to produce
>      Sam>  MSVC-compatible import libraries from a dll, but it is not difficult.
>
> I thought the mingw site had a procedure to turn a .a import library
> plus a dll into a .lib. but it may have used msvc tools under the
> covers.

Out of interest, will you be using MSVC exclusively or is it useful to 
have gcc support on Windows? Using the MS toolchain for the stub library 
would allow us to use a local exception handler to trap RPC exceptions, 
and although it would make the Makefile and the build requirements ugly 
I think this is unavoidable anyway if you need an import library generated.

Sam