Re: Help on TCP Remoting options:
From: Richard Blewett [DevelopMentor] (richardb_at_develop.com)
Date: 09/21/04
- Next message: tommys: "Get the CultureInfo object according to the OS settings..."
- Previous message: Ignacio Machin \( .NET/ C# MVP \): "Re: ref parameter for any object"
- In reply to: Ming Chen: "Re: Help on TCP Remoting options:"
- Next in thread: Nicholas Paldino [.NET/C# MVP]: "Re: Help on TCP Remoting options:"
- Messages sorted by: [ date ] [ thread ]
To: microsoft.public.dotnet.languages.csharp Date: Tue, 21 Sep 2004 11:03:32 -0700
For a server, the ability to remotely administer my server is a pretty crucial aspect. But agreed, due to the lack of an inbuilt security infrastructure in remoting, securing the control interface more than the line-of-business one would not be straightforward.
Regards
Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/ Yes, you are right. The remoting service can always be controlled with the
remoting interface it provides. But normally you would like the control
interface to be more secure than the service interface. For example, only
start/stop the service from localhost, not remotely.
Best Regards
Ming Chen
"Richard Blewett [DevelopMentor]" <richardb@develop.com> wrote in message
news:uJO%23qm$nEHA.3628@TK2MSFTNGP09.phx.gbl...
> Seeing as you are deploying a remoting component into the service, having
to communicate via an IPC is not really a problem
>
> Regards
>
> Richard Blewett - DevelopMentor
>
> http://staff.develop.com/richardb/weblog
>
>
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/
>
> Hi, Mural.
> Though windows service is a better choice most of the time, it actually
> depends on the nature of the service.
> The benefit of using a windows service as host is that the service can
> use a different user account, with less or greater privilege (more
> security); it can have a separate logon session; the service will be up
and
> running without anyone logon to the machine.
> On the other hand, windows service normally can't have any user
> interaction (can't access desktop, etc). If a system tray controller is
> required, it has to communicate with the service through any IPC.
> BTW: You also have the option of hosting a remoting object by ASP.NET.
>
> Hope this helps.
> Ming Chen
>
> "Mural Kumar via .NET 247" <anonymous@dotnet247.com> wrote in message
> news:ehQOfM$nEHA.2904@TK2MSFTNGP15.phx.gbl...
> > (Type your message here)
> >
> > --------------------------------
> > From: Mural Kumar
> >
> > Which is the best way to make a remoting
> > server?
> >
> > 1)As a Windows service
> > 2)As a simple exe, which will run in a system tray.
> >
> > If there is any link or article, please let me know.
> >
> > Thank you
> >
> > Mural
> >
> > -----------------------
> > Posted by a user from .NET 247 (http://www.dotnet247.com/)
> >
> > <Id>sysRNMGC40em7DQ50mPSEw==</Id>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004
>
>
>
> [microsoft.public.dotnet.languages.csharp]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004
[microsoft.public.dotnet.languages.csharp]
Relevant Pages
... The remoting service can always be controlled with the ... But normally you would like the control ... interface to be more secure than the service interface. ... > Though windows service is a better choice most of the time, ...
(microsoft.public.dotnet.languages.csharp)
... interface back to the client as .NET Remoting will try to create it (not ... BUT I doubt it will allow you to cast it to the interface in your DLL. ... Activate an interface but that is different than remoting an interface. ... > .Net Remoting is really a pain to work with for me. ...
(microsoft.public.dotnet.framework.remoting)
... my own custom objects which are for all intensive purposes an Interface ... IDE so happy to auto generate and overwrite any custom code you have written ... There has got to be a way for WSDL ... As for the remoting, I know what remoting is capable of ...
(microsoft.public.dotnet.framework.webservices)
... So if I have the remoting service set as SingleCall - it's ... it's not possible to instantiate a new ... Now implement this interface on the ... > only on the client). ...
(microsoft.public.dotnet.framework.remoting)
... using both "is" and "as" are unreliable when it comes to remoting objects ... the object actually implements the interface). ... FIRST class against which it is tested. ... remote object), then "o is D" will return false (since it is not the first ...
(microsoft.public.dotnet.framework.remoting)