On Dec 8, 9:03 pm, "Brandon Betances" <[EMAIL PROTECTED]> wrote:
> you lost me mate. explain more.
>
My initial query was sloppy. It's trivial
for a Windows client to create a proxy for a Web
service and then communicate with it. That's
not what I'm looking for!
What I really want is for a Web service on a
server to find a singleton Windows client
running on the same host machine that
can be used to display information about
the Web service and manipulate its
database.
In 25 words or less, I'd like to add a UI to a
Web service, and the service should be
able to push data to the UI.
For instance, this UI might show
that a certain remote host executed
a certain Web method. If the UI
were a simple console, then the
Web service uses its handle to the
console to do something like,
myOneAndOnlyConsole.WriteLine(String.Format("{0} logged in ",
GetRemoteHostName( ) );
where GetRemoteHostName is a private method defined
in the Web service.
An administrator would be the only user of the UI.
Does this make more sense?
