Re: Automatic startup of .NET server-side object?
From: Derrick (Derrick[underscore]Repep[at]toxicall[dot]com)
Date: 02/06/04
- Next message: Steven M. King: "Re: Determine context under which serializble object is running"
- Previous message: Jim Sievert: "Re: Determine context under which serializble object is running"
- In reply to: Sunny: "Re: Automatic startup of .NET server-side object?"
- Next in thread: Allen Anderson: "Re: Automatic startup of .NET server-side object?"
- Reply: Allen Anderson: "Re: Automatic startup of .NET server-side object?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 6 Feb 2004 13:31:54 -0500
Hi Sunny,
Thank you for your response. It cleared up several issues I had with
respect to the options I have available to me.
Given what you've said and what I have read in various books, my best option
is going to be a Windows service. I plan to use TCP to pass byte streams of
data from the client to the server, and I do not want to require a login
before startup (I am using a console app in my prototyping). So, let me ask
two questions:
1. Does a Windows service have access to the local file system? In other
words, can a service write a file on a local hard drive?
2. Can I implement an interface in a Windows service? I need the ability
to call methods with sets of arguments, and I believe an interface will give
me what I need, but cannot tell from the reading I've done whether this is
allowable in a Windows service.
TYVM,
Derrick
"Sunny" <sunnyask@icebergwireless.com> wrote in message
news:%23R4lqvN7DHA.2300@TK2MSFTNGP10.phx.gbl...
> Hi Derrick,
> These are 2 different things - one is the object itself, and the other
> is the remoting infrastructure, which listens for a calls and if
> necessary, creates the object. In DCOM world the second part is SCM.
>
> So, in order to have someone to listen for an incoming call (the
> server), you may create the remoting server as an windows service, or
> host the server in IIS. Or create a console app, which you run from
> Startup Folder.
>
> 1. Console app is not preferred, in order to start it, you have to log
> on to the machine. But it is good for development/debug purposes.
> 2. IIS - if you plan to use HTTP channels and build-in
> security/authentication of IIS
> 3. Windows service - this is the most convenient for internal use, and
> where you can reach the server with TCP channels. HTTP channel is only
> available with IIS hosting.
>
> Hope that helps
> Sunny
>
> In article <uejv2dN7DHA.1672@TK2MSFTNGP12.phx.gbl>, "Derrick" <Derrick
> [underscore]Repep[at]toxicall[dot]com> says...
> > Hi,
> >
> > Another basic question about .NET remoting:
> >
> > In the DCOM world (which, I know, is to be avoided like the plague), a
> > client application could make a DCOM call to the server and, if the
> > receiving (D)COM object was not started, the SCM would instantiate it.
In
> > the .NET remoting world, my preliminary investigations have shown me
that
> > the server has to be "listening" to the TCP / HTTP port when the call is
> > made, or an error is thrown.
> >
> > Is there a way to get the .NET server-side object to start automatically
if
> > it's not running when the call is made?
> >
> > TIA,
> > Derrick
> >
> >
> >
- Next message: Steven M. King: "Re: Determine context under which serializble object is running"
- Previous message: Jim Sievert: "Re: Determine context under which serializble object is running"
- In reply to: Sunny: "Re: Automatic startup of .NET server-side object?"
- Next in thread: Allen Anderson: "Re: Automatic startup of .NET server-side object?"
- Reply: Allen Anderson: "Re: Automatic startup of .NET server-side object?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
