Re: Web service invoking for a server / client app
- From: "Nicholas Paldino [.NET/C# MVP]" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Dec 2005 01:35:32 -0500
Jack,
Well, you seem to have a problem. You don't want to place code in your
web service methods themselves, because you want a centralized server to
handle it. At the same time, you don't want to make a call from the web
service to your centralized server.
You have to make a decision to use one or the other.
What you could do is have your service expose methods/objects through
remoting, and then use a cross-process channel on the same machine to access
the service. It should be pretty fast in that case.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
"Jack" <jack@xxxxxxxxxxx> wrote in message
news:u3Dod0VCGHA.3812@xxxxxxxxxxxxxxxxxxxxxxx
>I want to design a server which performs some business related user
>authentiation, and would like to let the clients invoke it through
>webservice, so my first thinking is using IIS as the web server to host
>webservice, but then how does it interact with my server. Another invoking
>from IIS to my server ? no way, it should be damn slow. The problem is I
>want my server to control many authentiation information, so I don't want
>them to be sparsed put into "every" webservice functions the client will
>invoke, instead a centralized server to do the logic. Can anyone give me
>some solutions for this scenario ?
>
>
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: overloading abstract type
- Next by Date: Re: Generate Client from Web Service
- Previous by thread: Web service invoking for a server / client app
- Next by thread: Re: Web service invoking for a server / client app
- Index(es):
Relevant Pages
|