On Dec 8, 2:03 pm, Stratum <[EMAIL PROTECTED]> wrote:
> Here's an interesting problem.
>
> I have a Web service that I sometimes want to
> monitor at the server computer by calling up a
> Windows client to see activity in real time.
> Who's logged in, what's s/he doing, how
> long does he spend, etc. I might also want
> to use this "local client" to edit
> the service's database. I *could* do this
> by adding a privately accessed page to the
> Web service that only an administrator
> knows about.
>
> But I'm adventurous and I want this
> one-time Window client that doesn't
> exist on any other computer.
>
> So I build a Web service project and
> in the same solution add a Windows
> project. (It could also be a Console
> project.) I deploy the Web service
> and now and then sit at the
> server computer and start the
> Windows client as a singleton.
>
> Here's the question...
>
> From the Window client, how
> do I access the Web service,
> and monitor sessions? As a
> ground rule, we'll say that all
> Windows - Web service
> communications are initiated
> on the Windows side. The
> Web service has no knowledge
> of the Windows client.
>
> I'm probably making too big a
> deal about this. Anybody got
> an idea? Done something
> similar?
Erm, I've changed the architecture a bit.
I would like a Web service to be able
to find a singleton Windows client, if it
exists, on the same machine and write
messages to it.
