ClientBase.Close is blocking

After I solved my OneWay problem I hit another. My client basically
goes like this:

Create Client
Call a oneway method
Client.Close();

The oneway now returns fine - but the close blocks until the process in
the oneway call on the server returns back. This could be by design,
and if so thats fine.

1) I thought about removing close - but the problem is there are many
servers from this object and I have no idea when I could close it, some
processes may run a long time even after the object client is disposed
of.

2) I've changed the server process to use a threadpool call to do its
ow oneway of sorts on the server. This seems to work fine.

Any other suggestions that I should consider?

--
"Programming is an art form that fights back"
http://www.KudzuWorld.com/
Need a professoinal technical speaker at your event? See www.woo-hoo.net

Chad!
Just a question/hint did you close Host before Client.Close() ?
Arkady

"Chad Z. Hower" <chad-ng@hower.org> wrote in message
news:uxkLPG84GHA.2596@TK2MSFTNGP06.phx.gbl...
> After I solved my OneWay problem I hit another. My client basically
> goes like this:
>
> Create Client
> Call a oneway method
> Client.Close();
>
> The oneway now returns fine - but the close blocks until the process in
> the oneway call on the server returns back. This could be by design,
> and if so thats fine.
>
> 1) I thought about removing close - but the problem is there are many
> servers from this object and I have no idea when I could close it, some
> processes may run a long time even after the object client is disposed
> of.
>
> 2) I've changed the server process to use a threadpool call to do its
> ow oneway of sorts on the server. This seems to work fine.
>
> Any other suggestions that I should consider?
>
> --
> "Programming is an art form that fights back"
> http://www.KudzuWorld.com/
> Need a professoinal technical speaker at your event? See www.woo-hoo.net