Web service architecture issue

[ghause]

I am writing what is essentially a facade layer for service consumption. I
don't want this facade to be part of my web application, it needs to be a
standalone dll. This facade will contain all of my web references and public
methods exposing them to my web app.

In addition to calling the web services asynchronously is there anything I
can do to ensure the best performance possible?

Should I write a PreRequestHandler, and if I do how can I best isolate it
from the web project?

[John Saunders]

"ghause" <gh****@discussions.microsoft.comwrote in message
news:1E**********************************@microsof t.com...

>I am writing what is essentially a facade layer for service consumption. I
don't want this facade to be part of my web application, it needs to be a
standalone dll. This facade will contain all of my web references and
public
methods exposing them to my web app.

In addition to calling the web services asynchronously is there anything I
can do to ensure the best performance possible?

Should I write a PreRequestHandler, and if I do how can I best isolate it
from the web project?

Why do you assume that you'll have a performance problem, and why do you
assume that calling the service asynchronously will solve the problem that
you assume you have?

John

[Gaurav Vaish \(www.EduJiniOnline.com\)]

>I am writing what is essentially a facade layer for service consumption. I

don't want this facade to be part of my web application, it needs to be a
standalone dll. This facade will contain all of my web references and
public
methods exposing them to my web app.

Do you mean that this main web-service will be the interceptor for other
web-services?

If that's so, I would suggess looking into something known as
WS-Addressing (the standard that supersedes WS-Routing). Although
implementing it would require WSE but then that's a standard and everybody
uses it.

It would also help you away from your-facade-service-specific issues.

In addition to calling the web services asynchronously is there anything I
can do to ensure the best performance possible?

Nopes. There's nothing special about aync calling. It's something like
starting it in a new thread on the client side. How does the server know
whether or not the call is async?

Should I write a PreRequestHandler, and if I do how can I best isolate it
from the web project?

For what? What do you plan to do there?
--
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.com
http://articles.edujinionline.com/webservices
-------------------