Web service invoking for a server / client app

[Jack]

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 ?

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

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]
- mv*@spam.guard.caspershouse.com

"Jack" <jack@no_spam.com> wrote in message
news:u3**************@TK2MSFTNGP15.phx.gbl...

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 ?

[Jack]

Thanks Nicholas,

Is it complicated my server implements webservice itself without IIS. I
think the dotnet framework is built in such stuff. I've to implement about
40 web service methods in total.

I've 2 choices now.

1. Implement WS in IIS and using remoting to access my SAO.
2. Client is in IIS, and call my server implemented webservice.

Jack

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:Oi**************@TK2MSFTNGP11.phx.gbl...

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]
- mv*@spam.guard.caspershouse.com

"Jack" <jack@no_spam.com> wrote in message
news:u3**************@TK2MSFTNGP15.phx.gbl...

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 ?