ASMX and ASPX in same application ?

[Navin Mishra]

Hi,

Are there any implications of having ASMX and ASPX in same ASP.NET
application ? Both would share the same global varriables, etc.

Regards

Navin

 

[Scott M.]

Functionally no. But from a design standpoint, yes.

The whole point of a web service is to have a non-proprietarty,
platform-independant way to do remote procedure calls via http. If the GUI
and the service are on the same box, you don't need what web services offer
and, in fact, would most likely be degrading the overall performance of the
application.

-Scott

 

[Navin Mishra]

Thanks for quick response. Could you shed more light on how it could degrade
overall performance ? May be because ASP.NET ThreadPool threads are shared
between the two ? The ASMX need to return actually the URL of ASPX to the
user which user could put in a browser. There may be some data retrieved
from 3rd party which ASPX and ASMX may need to share and that's why I was
thinking of putting them in same application.

Thanks again and regards

Navin

 

[agapeton]

You'll want to create your web services and then wrap it with a
separate ASP.NET page. That's a pretty standard model.

 

[Scott M.]

Web services offer platform indepenance and non-proprietary ways of
communicating, but there is a cost - serialization and bandwith. It has
notihing to do with threads and URL's. The data passed to a web service and
the response coming back are done in XML using the SOAP protocol. While
definately an "open" model, no one ever touted web services as the best
performing solution to cross-platform remote procedure calls. As a result,
there is an inherant performance limitation to them.

If you need to call a procedure from the same box as the GUI, then just
create a regular .NET class and call functions of that class. Web Services
are for calling procedures (functions) on other boxes in a non-proprietary,
platform-independant way. Because of this, most applications are built in
"tiers", with different tiers residing on different boxes. This is done for
security and scalability.

-Scott