|
|
Back to UserFriendly Strip Comments Index
|
.NET remoting and events... | by MrTrick | 2006-10-26 18:31:36 |
|
Somewhat experienced... | by bwkaz | 2006-11-19 12:55:59 |
|
Thanks, I'll look through it. | by MrTrick | 2006-10-26 18:47:41 |
|
Well, with remoting, there *is* no persistent | by bwkaz | 2006-10-26 18:54:01 |
|
*blink* | by MrTrick | 2006-10-26 19:20:56 |
| ... OK, you have me there, I'm not sure. |
by bwkaz |
2006-10-26 19:38:22 |
I know that the setup I had (with no events) doesn't keep connections around to the clients. (I was wondering why proxies didn't implement IDisposable to clean up the socket, and why I couldn't get at the proxy itself if it did. Then I realized -- with some help from tcpview -- that there was no socket after a while.) Maybe I had a single-call object, though? Well, no, it had state that it kept around on the server. Hmm. It was a singleton, if that matters.
Anyway, I could see passing another MarshalByRefObject to the server (which is what you started with); it should turn into a proxy when the server deserializes the parameter, and the proxy should know how to contact the client. But if you say that's causing problems with security... I guess I'm not really sure how it should work. |
|
[ Reply ] |
|
And it's just about TTGTB. | by bwkaz | 2006-10-26 19:53:44 |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|