Server.Transfer() : customer is appeared as it is on the asking for page
just, yet the all the substance is of the asked for page. Information can be
continue accros the pages utilizing Context.Item gathering, which is one of
the most ideal approach to exchange information starting with one page then onto the next keeping the page
state alive.
Response.Dedirect() :customer know the physical area (page name and
inquiry string also). Context.Items loses the persisitance when
nevigate to goal page. In prior forms of IIS, on the off chance that we needed
to send a client to another Web page, the main choice we had was
Response.Redirect. While this strategy accomplishes our objective, it has
a few critical disadvantages. The most serious issue is that this strategy
causes every page to be dealt with as a different exchange. Other than
making it hard to keep up your value-based trustworthiness,
Response.Redirect presents some extra cerebral pains. To begin with, it
averts great epitome of code. Second, you lose access to all of
the properties in the Request question. Of course, there are workarounds, yet
they're troublesome. At long last, Response.Redirect requires a round excursion
to the customer, which, on high-volume locales, causes adaptability
issues. As you may associate, Server.Transfer settles all with these
issues. It does this by playing out the exchange on the server without
requiring a roundtrip to the customer.
· Can you give a case of when it is proper to utilize a
web benefit instead of a non-adjusted
.NET part?
Conveying through a Firewall When assembling an appropriated
application with 100s/1000s of clients spread over various areas,
there is dependably the issue of conveying amongst customer and server
due to firewalls and intermediary servers. Uncovering your center level
parts as Web Services and summoning the straightforwardly from a Windows UI
is an exceptionally substantial choice.
Application Integration When incorporating applications written in
different dialects and running on unique frameworks. Then again even
applications running on a similar stage that have been composed by
isolate merchants.
Business-to-Business Integration This is an empowering influence for B2B
intergtation which permits one to uncover imperative business procedures to
approved provider and clients. An illustration would uncover
electronic requesting and invoicing, permitting clients to send you
buy requests and providers to send you solicitations electronically.
Programming Reuse This happens at numerous levels. Code Reuse at the
Source code level or paired componet-based resuse. The constraining variable
here is that you can reuse the code however not the information behind it.
Webservice conquer this restriction. A situation could be the point at which you are
building an application that totals the usefulness of serveral other
Applicatons. Each of these capacities could be performed by person
applications, however there is esteem in maybe joining the different applications to
introduce a unifiend see in a Portal or Intranet.
At the point when not to utilize Web Services: Single machine Applicatons When the applications
are running on a similar machine and need to speak with each other
utilize a local API. You additionally have the choices of utilizing part
innovations, for example, COM or .NET Componets as there is practically nothing
overhead.
Homogeneous Applications on a LAN If you have Win32 or Winforms applications
that need to convey to their server partner. It is substantially more
proficient to utilize DCOM on account of Win32 applications and .NET Remoting in
the instance of .NET Apps
· Can you give a case of what may be most appropriate to put in
the Application_Start and Session_Start subroutines?
The Application_Start occasion is ensured to happen just once all through
the lifetime of the application. It's a decent place to instate worldwide
factors. For instance, you might need to recover a rundown of items
from a database table and place the rundown in application state or the
Store question. SessionStateModule uncovered both Session_Start and
Session_End occasions.
