Help on TCP Remoting options:

[Mural Kumar via .NET 247]

(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>

[Ming Chen]

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" <an*******@dotnet247.com> wrote in message
news:eh**************@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>

[Nicholas Paldino [.NET/C# MVP]]

Mural,

It really depends on what you are trying to do. If the remoted objects
are only going to be interacted with by someone on the same machine, during
a user session, then the second option is better. However, if this is a
service, where people will connect to it regardless of the user session
logged into the service machine, then the first option is better.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Mural Kumar via .NET 247" <an*******@dotnet247.com> wrote in message
news:eh**************@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>

[Richard Blewett [DevelopMentor]]

This is really a qustion of whether you only want the applkication to run when someone is logged on to the machine. For peer-2-peer this is perfectly acceptable. However, for a server app you really don't want someone to go have to log on to the machine for the server to be able respond to requests. A service can run without someone logged on, a system tray application cannot.

Regards

Richard Blewett - DevelopMentor

http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<eh**************@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]

[Richard Blewett [DevelopMentor]]

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/<O4**************@TK2MSFTNGP11.phx.gbl>

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" <an*******@dotnet247.com> wrote in message
news:eh**************@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]

[Willy Denoyette [MVP]]

"Richard Blewett [DevelopMentor]" <ri******@develop.com> wrote in message
news:eg**************@TK2MSFTNGP10.phx.gbl...

A service can run without someone logged on, a .....

Richard,

The same goes for a console applications started as a scheduled task.

Willy.

[Richard Blewett [DevelopMentor]]

Ah yes, thats true.

Although are you suggesting that a timed console app is a good alternative to a windows service as a remoting host?

Regards

Richard Blewett - DevelopMentor

http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<#V**************@TK2MSFTNGP11.phx.gbl>
"Richard Blewett [DevelopMentor]" <ri******@develop.com> wrote in message
news:eg**************@TK2MSFTNGP10.phx.gbl...

A service can run without someone logged on, a .....

Richard,

The same goes for a console applications started as a scheduled task.

Willy.


---
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]

[Ming Chen]

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]" <ri******@develop.com> wrote in message
news:uJ****************@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/<O4**************@TK2MSFTNGP11.phx.gbl>
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" <an*******@dotnet247.com> wrote in message
news:eh**************@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]

[Richard Blewett [DevelopMentor]]

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/<uvbmYK Ao********@TK2MSFTNGP11.phx.gbl>

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]" <ri******@develop.com> wrote in message
news:uJ****************@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/<O4**************@TK2MSFTNGP11.phx.gbl>
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" <an*******@dotnet247.com> wrote in message
news:eh**************@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]

[Willy Denoyette [MVP]]

In my opinion Yes, I find in general that Windows Services are way overused.
Scheduled tasks can offer a good alternative for services, especially for
simple tasks like remoting hosts.
After all they share most of the "features" like:
- Run in a configurable security context (user)
- No UI (sandboxed desktop/winstation) when run in the LocalSystem context.
- Can easily be controlled just like services (started , stopped, queried,
changed...)
But also offers some advantages not found when implemented as a Service:
- Less complex to implement, you don't have to consider specific SCM
requirements like OnStart/OnStart time-out's . The FCL hides most of the
complexities of the SCM interaction protocol, but many inexperienced
developers do have issues with it, just because so many things are hidden
,but he! they still are there under the covers (very often the cause of
services failing to start or stop).
- And they can be scheduled to run at boot time, logon time, system idle
time or at specific date/time, which is less flexible when running as a
service.

Willy.

"Richard Blewett [DevelopMentor]" <ri******@develop.com> wrote in message
news:uL**************@TK2MSFTNGP12.phx.gbl...

Ah yes, thats true.

Although are you suggesting that a timed console app is a good alternative
to a windows service as a remoting host?

Regards

Richard Blewett - DevelopMentor

http://staff.develop.com/richardb/weblog
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<#V**************@TK2MSFTNGP11.phx.gbl>
"Richard Blewett [DevelopMentor]" <ri******@develop.com> wrote in message
news:eg**************@TK2MSFTNGP10.phx.gbl...

A service can run without someone logged on, a .....

Richard,

The same goes for a console applications started as a scheduled task.

Willy.


---
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]

[Ravichandran J.V.]

Between the two, a normal exe is a better option.

with regards,
J.V.Ravichandran
- http://www.geocities.com/
jvravichandran
- http://www.411asp.net/func/search?
qry=Ravichandran+J.V.&cob=aspnetpro
- http://www.southasianoutlook.com
- http://www.MSDNAA.Net
- http://www.csharphelp.com
- http://www.poetry.com/Publications/
display.asp?ID=P3966388&BN=999&PN=2
- Or, just search on "J.V.Ravichandran"
at http://www.Google.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Richard Blewett [DevelopMentor]]

Well I disagree. The ability to have the process run unattended *and* have a control interafce familiar to all machine admins is a big plus - even if the code is slightly more complex. As already stated the complexities of service programming have been buried in the framework for the most part.

Regards

Richard Blewett - DevelopMentor

http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/<eA*************@tk2msftngp13.phx.gbl>

Between the two, a normal exe is a better option.

with regards,
J.V.Ravichandran
- http://www.geocities.com/
jvravichandran
- http://www.411asp.net/func/search?
qry=Ravichandran+J.V.&cob=aspnetpro
- http://www.southasianoutlook.com
- http://www.MSDNAA.Net
- http://www.csharphelp.com
- http://www.poetry.com/Publications/
display.asp?ID=P3966388&BN=999&PN=2
- Or, just search on "J.V.Ravichandran"
at http://www.Google.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

---
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]

[Ravichandran J.V.]

The complexities of Service development may be buried within the .Net
framework but the access to some of the OS' resources for the Windows
Service does cause a concern for them to be used in Remoting.
Permissions, account under which the Service runs etc.

with regards,
J.V.Ravichandran
- http://www.geocities.com/
jvravichandran
- http://www.411asp.net/func/search?
qry=Ravichandran+J.V.&cob=aspnetpro
- http://www.southasianoutlook.com
- http://www.MSDNAA.Net
- http://www.csharphelp.com
- http://www.poetry.com/Publications/
display.asp?ID=P3966388&BN=999&PN=2
- Or, just search on "J.V.Ravichandran"
at http://www.Google.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!