Architecture/Design Question

[Picho]

Hi guys,

I am planning on building a rather large (in terms of publicly visible
methods) distributed application.

since the user (rich) windows forms client uses the application from inside
and outside the LAN, I thought of exposing these methods as webMethods
categorized into web services (instead of remoting I should point out -
which was the other option).

my initial thought was to create a windows service that will host the server
application. the webMethods will 'talk' to the service in order to execute
the commands (thus making the web services only wrappers around te service
itself).
in addition there will be an administrative application (like a control
panel) for configuring and monitoring the service.

Please make comments about this and offer other design options for me to
consider.
How do you think a web service should communicate with a windows service
running on the same machine?
is remoting the only option?
I understand that VS2005 offers a new remoting cahnnel - IPC. does this
apply here?

Thanx in advance,
Picho

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

Picho,

If the web service is going to be exposed from the same machine that the
service is on, then you can use the IPC channel.

I am curious though, why not just make the web service the service? Why
have the overhead of another service?

Since the web service is going to be the entry point for everything, I
don't see the need for the additional service. You can place methods on the
web service to change the nature of how it operates (your administrative
application).

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

"Picho" <SP********@telhai.ac.il> wrote in message
news:uO**************@TK2MSFTNGP10.phx.gbl...

Hi guys,

I am planning on building a rather large (in terms of publicly visible
methods) distributed application.

since the user (rich) windows forms client uses the application from
inside and outside the LAN, I thought of exposing these methods as
webMethods categorized into web services (instead of remoting I should
point out - which was the other option).

my initial thought was to create a windows service that will host the
server application. the webMethods will 'talk' to the service in order to
execute the commands (thus making the web services only wrappers around te
service itself).
in addition there will be an administrative application (like a control
panel) for configuring and monitoring the service.

Please make comments about this and offer other design options for me to
consider.
How do you think a web service should communicate with a windows service
running on the same machine?
is remoting the only option?
I understand that VS2005 offers a new remoting cahnnel - IPC. does this
apply here?

Thanx in advance,
Picho

[Picho]

Thanks for the reply Nicholas.

I realy do not have a good answer to that. It might be just me feeling
uncomfertable doing in in an IIS application (thats what it is after all...)
But I would like to hear what you propose. If you can develope this
direction a bit.

thanks again,
Picho
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:Op**************@TK2MSFTNGP10.phx.gbl...

Picho,

If the web service is going to be exposed from the same machine that
the service is on, then you can use the IPC channel.

I am curious though, why not just make the web service the service?
Why have the overhead of another service?

Since the web service is going to be the entry point for everything, I
don't see the need for the additional service. You can place methods on
the web service to change the nature of how it operates (your
administrative application).

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

"Picho" <SP********@telhai.ac.il> wrote in message
news:uO**************@TK2MSFTNGP10.phx.gbl...

Hi guys,

I am planning on building a rather large (in terms of publicly visible
methods) distributed application.

since the user (rich) windows forms client uses the application from
inside and outside the LAN, I thought of exposing these methods as
webMethods categorized into web services (instead of remoting I should
point out - which was the other option).

my initial thought was to create a windows service that will host the
server application. the webMethods will 'talk' to the service in order to
execute the commands (thus making the web services only wrappers around
te service itself).
in addition there will be an administrative application (like a control
panel) for configuring and monitoring the service.

Please make comments about this and offer other design options for me to
consider.
How do you think a web service should communicate with a windows service
running on the same machine?
is remoting the only option?
I understand that VS2005 offers a new remoting cahnnel - IPC. does this
apply here?

Thanx in advance,
Picho

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

Picho,

I would say the service is justified if you are going to use it to
process some long-running request, and the web service will be used to
initiate the operation. Other than that, I would just have the web requests
handle everything.

I would use a service if I needed it to perform work outside of what is
directly requested by the web services.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Picho" <SP********@telhai.ac.il> wrote in message
news:es**************@tk2msftngp13.phx.gbl...

Thanks for the reply Nicholas.

I realy do not have a good answer to that. It might be just me feeling
uncomfertable doing in in an IIS application (thats what it is after
all...)
But I would like to hear what you propose. If you can develope this
direction a bit.

thanks again,
Picho
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote
in message news:Op**************@TK2MSFTNGP10.phx.gbl...

Picho,

If the web service is going to be exposed from the same machine that
the service is on, then you can use the IPC channel.

I am curious though, why not just make the web service the service?
Why have the overhead of another service?

Since the web service is going to be the entry point for everything, I
don't see the need for the additional service. You can place methods on
the web service to change the nature of how it operates (your
administrative application).

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

"Picho" <SP********@telhai.ac.il> wrote in message
news:uO**************@TK2MSFTNGP10.phx.gbl...

Hi guys,

I am planning on building a rather large (in terms of publicly visible
methods) distributed application.

since the user (rich) windows forms client uses the application from
inside and outside the LAN, I thought of exposing these methods as
webMethods categorized into web services (instead of remoting I should
point out - which was the other option).

my initial thought was to create a windows service that will host the
server application. the webMethods will 'talk' to the service in order
to execute the commands (thus making the web services only wrappers
around te service itself).
in addition there will be an administrative application (like a control
panel) for configuring and monitoring the service.

Please make comments about this and offer other design options for me to
consider.
How do you think a web service should communicate with a windows service
running on the same machine?
is remoting the only option?
I understand that VS2005 offers a new remoting cahnnel - IPC. does this
apply here?

Thanx in advance,
Picho