Home » Category » DotNet

DotNet: yet another remoting & events question

100| Mon, 24 Dec 2007 00:50:00 GMT| stevewhitley| Comments (1)
in the spirit of beating a dead hose (with such a blatently repeated

topic) and as a result of my CLS (chronic lazyness syndrome) condition:

given the following interface:

public interface IStatusProvider {

void UpdateStatus(StatusArgs e);

event EventHander<StatusArgs> StatusRecieved;

}

I want to be able to sync up some servers using one of 2 methods.

I'm trying to see what would be easier / more efficient: just

broadcasting a UDP status message or using remoting /w events.

I know that there is different types of remoting (client activated,

server activated blah blah blah), but will there be issues w/ using one

type over the other if you have events? I'd assume that I'd need

a persisted connection to use events. which is kind of a downer,

but using udp is unreliable so its 6 of 1 half dozen of another, so

here I am.

so, (briefly) what would I need to do to use this given that I have 6

identical servers running that need to know about each other. Is

it just a matter of registering a tcp server channel and attaching to

the event (calling the method when my status changes), or is it going

to be more than that. also, I've seen timeouts / null

reference exceptions that happen (in the limited remoting I have used)

when my marshal by ref object does not override

InitializeLifetimeService and return null.

thx for reading.

--Steve

Keywords & Tags: remoting, events, dotnet, .net

URL: http://dotnet.itags.org/dotnet-tech/294/
 
«« Prev - Next »» 1 helpful answers below.
well, I can only guess that since this got moved to a forum that nobody ever visits, I'll never get a response...

thanks anyway I guess.

stevewhitley | Fri, 31 Aug 2007 03:10:00 GMT |

DotNet Hot Answers

DotNet New questions

DotNet Related Categories