Server + Multiple Clients + Notify specific client -- dotnet remoting

mtv
4/6/2006 10:35:01 AM

James,

Let me first try to re-cap what you're asking. Let me know if it's not what
you're looking for.

You want to have your server object fire specific events to a specific
client(s) who subscribe to such events. There are two ways that I know:

1/ Client register event callback handler with server. This option limits a
fixed number of event types that must be known at design time (i.e. NewData,
DataRemoved...). With this option:

Client <--> Common Abstract class (CAC) <--> Server
Client class inherits from CAC
Server class inherits from CAC

AbstractClient is registered with Server --> Server's event is sent to
AbstractClient handler which will in turns calls Client's method.

Here are some of the links for more details:
http://www.codeproject.com/csharp/RemotingAndEvents.asp
http://www.dotnetspider.com/kb/Article565.aspx

2/ Server just have to maintain a "table" of clients <--> events and
broadcast messages to only subscribed clients upon an event. This allows you
to manage event types and users at any time since event/clients... are just
data to the application.

Good luck.

--
Your 2 cents are worth $milion$. Thanks.

[quoted text, click to view]

James Hancock
4/6/2006 4:15:31 PM

Ok, so I've pretty much figred out that I needed to do what you said I
needed to do :)

So I created an archetecture like so:

Server > ServerWrapper > ClientWrapper > Client

The client instantiates ClientWrapper and passes itself using a interface
that is available in the central DLL that holds the Server Wrapper and
Client Wrapper.

The server instantiates a new Server Wrapper on it's side with the shared
DLL.
When the server needs to notify the client it raises an event in
ServerWrapper which the clientwrapper is subscribed to because it
instantiates a ServerWrapper to. It then notifies the Client via the
interfaced method call of the event and then the client responds.

All would be great, and method calls Client to ClientWrapper to
serverWrapper to Server work fine and dandy.

However, the event from the server gets killed in the server ServerWrapper
because it says it can't find the DLL that hte ServerWrapper and
ClientWrapper are in. (i.e. the function is in the dll that it says that it
can't find)

Do you or anyone else have any ideas on why it is telling me that it can't
locate the dll when it's in that dll?

ServerWraper and ClientWrapper are marked as serializable and everything.

Thanks!
James Hancock

[quoted text, click to view]

mtv
4/7/2006 6:49:02 AM

I think you got the idea; however, your implementation is not there yet. Keep
in mind we're talking at high-level here, and that's why it's better to
follow/study the links I sent you.

At the high level, you should have:
ServerObj inherits from AbtractServerObj.
ClientObj inherits from AbstractClientObj: AbstractClientObj should have 2
methods:
1/ "Inline" method: MyEventHandler(...) { call ClientHandler(...); }
2/ Abstract method: ClientHandler(...) that is overridden by ClientObj.

Have both AbstractServeObj and AbstractClientObj built in 1 dll --> both
ServerObj and ClientObj can see the interface (that's all you need for a
proxy).

So, Client application instantiate ClientObj typecasted to
AbstractClientObj. Client app create remote ServerObj and has its proxy as
AbstractServerObj. Register event with its clientObject.MyEventHandler(). So
now, when server object fires an event, the event is sent to MyEvntHandler
which in turns calls ClientHandler() that resides on client app's domain.

More details should be looked into the links.

Have fun.

--
Your 2 cents are worth $milion$. Thanks.

[quoted text, click to view]

James Hancock
4/10/2006 4:15:55 PM

Thanks,

I've read both of those articles and I'm still at a loss as to why I'm
getting the error message.

See if I invoke a method on the client side it gets raised on the server
which raises the event in the main Server Service class that runs as a
Windows Service no problem and all is good.

It's only when sending a message to the client by raising an event that I
get an error. And the error occurs in the very file that it says it can't
find. I shouldn't need a server Interface when sending an event from what
I'm reading in those articles, only when receiving events from the clients,
which I'm not really doing because I'm calling the methods.

The good thing in those articles is the use of the Dispatch system, which
I'm definately going to impliment, but I'm still trying to figure out what
I'm missing with the error I'm getting given that I have a client interface
and everything.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet remoting

dotnet remoting : Server + Multiple Clients + Notify specific client