Re: How To Create "Out Of Process" Components
- From: "Brian Gideon" <briangideon@xxxxxxxxx>
- Date: 2 May 2005 07:51:16 -0700
Ulrich,
My comments are inline.
Brian
Henne wrote:
> Hello Brian,
>
> thanks for your reply.
>
> For me, remoting always was a call on a business component that will
> do something, return a value and then is gone.
That's the behavior you get with a server activated object (SAO) that
is setup with the WellKnownObjectMode.SingleCall option. The
WellKnownObjectMode.Singleton option will allow clients to participate
in the lifetime of the object. I'm strictly speaking about the
lifetime of the remoted object here. The lifetime of the host process
is a different issue.
> What I am looking for is a component with a windows front end or
> let's say a windows application with an external control inteface.
> This application should stay alive as long the calling application
> has a link to it.
This is definitely doable with .NET Remoting.
> For me it is not clear if this will still be the right way.
> If yes, should I write my own hosting application or use IIS?
If you use IIS then you will need IIS installed on every machine your
remotable application runs on.
> Thanks in advance.
>
> Best regards
>
> Ulrich
>
.
- References:
- Re: How To Create "Out Of Process" Components
- From: Henne
- Re: How To Create "Out Of Process" Components
- Prev by Date: Re: Where is the "Setup"type of project in VisualC# 2005?
- Next by Date: Re: How to code Unicode strings in VB in dot net?
- Previous by thread: Re: How To Create "Out Of Process" Components
- Next by thread: Re: Server monitor and notification
- Index(es):
Relevant Pages
|
