remoting design

  • Thread starter Thread starter Sharon
  • Start date Start date
S

Sharon

Hi to all.
I have a server app. to which i need administration client.
The client will connect to the server via remoting.
I'm thinking of making one class on the server to serve the admin client.
Since the client must be authenticated, each method call will have to
include a session id, given to the client after a successful login.
If you know of a better way to do this, please let me know.
Thanks, Sharon.
 
Currently, I would tend to favor WSE (tcp or http) or Web Services for your
management apis. Has broader reach and has various security built in so you
don't have to build it all yourself. Once you have your WSE interface, then
it works for local clients and/or INET clients and cross-platform clients,
so you leverage your work which is big. Even thou Remoting tends to be
faster (as binary instead of xml), versioning your app is the real killer.
Web Methods are easy to version and a lot more flexible. Moreover, the road
to Indigo is via WSE/Web Services so it "should" be easier to port to Indigo
(next version of remoting, web services, wse, etc in a *single can) if you
wanted to at some point. Pretty good DotNet Show on this very thing below.
Don Box also has various papers on this subject (google em.) HTH
http://msdn.microsoft.com/theshow/episode046/default.asp
 
Let me also give Doug Purdy his props. Gotta love Doug Purdy (even if he
scared the &$@ out of me in one of recent blog posts with one of those
monsters that pop out at you...)
 
Back
Top