Re: Intercepting asp call and talking with Browser and IIS

Tech-Archive recommends: Fix windows errors by optimizing your registry

On 11 Jun 2006 04:19:56 -0700, pamelafluente@xxxxxxxxx wrote:

I would be grateful if you could give indications on how to implement
the key parts of this architecture (intercepting the info associated to
submit or other asp call and the talking back with the browser and in
case sending something to IIS). Pointer to demos or code snippets are
particularly appreciated.

Things are not as simple as that. When a button submits data to a site,
the page expects to receive data back, and essentially considers the
existing page to be gone. This means you *HAVE* to send back the original
page if you use a normal submit process and want the same page to stay
there.

There are other options, but they are greatly more complicated. For
example, you can use Ajax, which is essentially javascripted code to submit
a request and then do whatever you like.

Another option is to use ActiveX or Java/.net applets on the client.

You really need to have a better idea of what it is you are trying to
accomplish so that you can choose the right technique. What you've written
so far is very vague.

Start here:

http://atlas.asp.net/Default.aspx?tabid=47
.

Quantcast