P
pamelafluente
I am new to asp.net.
I have an asp page with a submit button which sends out some
information.
Instead of having IIS to respond and deal with this information, I
would like to have a .NET program (for instance a .NET service, or even
a client .net application) which is able to intercept this call and
deal with the associate information. This middle application might
decide whether to send something to IIS or just do everything by itself
and respond to the browser..
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.
-Pam
I have an asp page with a submit button which sends out some
information.
Instead of having IIS to respond and deal with this information, I
would like to have a .NET program (for instance a .NET service, or even
a client .net application) which is able to intercept this call and
deal with the associate information. This middle application might
decide whether to send something to IIS or just do everything by itself
and respond to the browser..
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.
-Pam