Design Question on using Remoting

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Microsoft News (Name_at_coxinet.net)
Date: 12/18/04 

Date: Sat, 18 Dec 2004 09:39:44 -0600

Currently I have an application that is quite large. It is all created in
VB.Net and is a Windows application. All the data push and pull is through
a VB.Net DLL. What I want to do is enable clients to continue to use my
windows base application but be able to connect to the database over the
internet. I have thought of many ideas and ruled most out. It is not
reasonable to re-write my application as a web base application, not going
to use web services, so in the en I am thinking of doing it with remoting.

My questions to you who have done remoting (And we have done some remoting
but it is connection to some remote procedures on the same network sitting
on a server. So I am a little familiar with remoting)

My architecture design thought is to take my Data.DLL and pull out the
functions (that do the database select, inserts, delete, and update) put
them in a remoting. Then all applications would call thought TCP to the
server and access the procedures on the server. For security I would
encrypt and compress the calls to and from the Remote procedures. So I
would have a thin layer that would take the calls (the parameter list and
data) from the client and the data coming back, encrypt the data and
compress it.

But I think most of my code would stay the same in the Data.DLL, my business
DLL would have to change to compress and uncompress the data etc.

Any advice on this design would be helpful. And yes I have to encrypt and
compress the information. It is highly sensitive information. Any ideas of
things to look out for, where to pay attention to, good examples/books to
help?

Also, what type of speed and performance will remote get me. I know this
will be much slower than the way it is now, connecting across a network
without remoting in the middle.

Thanks in advance

Clyde

Relevant Pages

  • RE: Is WindowsPrincipal is Remotable ?
    ... here's a link talking about securing a Remoting ... .NET 2.0 adds a number of security related features to Remoting: ... > using Server activated Remoting. ... > change this as Windows service does my security logic (passing windows ...
    (microsoft.public.dotnet.security)
  • Re: Is WindowsPrincipal is Remotable ?
    ... i guess you are using remoting - the security story of remoting is, well, ... Remoting has no authentication, authorization, message security ... server, the client opens a port and takes connections from the world... ... I'm developing a Windows based application in c#. ...
    (microsoft.public.dotnet.security)
  • ASP.NET app on IIS6 fails on .NET remoting call. Not on IIS5.1.
    ... I have a remoting server running as a service on a Windows XP ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Windows service vs. IIS service
    ... if you are going to use a proprietary protocol, the way to go is windows ... You don't need even remoting, ... > I have to port a server from Unix to the Windows world and plan to use .NET. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Windows service vs. IIS service
    ... if you are going to use a proprietary protocol, the way to go is windows ... You don't need even remoting, ... > I have to port a server from Unix to the Windows world and plan to use .NET. ...
    (microsoft.public.dotnet.framework)