L
lisa
One of the things I hate the most about ASP.NET is the postback of an
entire page just to update a single field. So I was looking around,
and I came across Remote Scripting.
See, when I write ASP pages, I usually have a hidden iframe on the page
that I post to. And onload, that hidden page copies the results back
up to the parent. I work in an IE only environment, so I can get away
with that.
And it's nice. Seamless. It's nice for the user, and I don't have to
deal with refilling fields unnecessarily.
But the same trick doesn't work with ASP.NET, because it's server
based. Remote Scripting, in theory, should do much the same thing.
So here are my questions:
* Have any of you worked with Remote Scripting in your ASP.NET apps?
* Is it worth it? Is it a mess? If I decide to jump into the deep
end, am I going to regret it, or is this a practical solution?
Opinions for and against are welcome. I'm wholly ignorant on the
subject.
entire page just to update a single field. So I was looking around,
and I came across Remote Scripting.
See, when I write ASP pages, I usually have a hidden iframe on the page
that I post to. And onload, that hidden page copies the results back
up to the parent. I work in an IE only environment, so I can get away
with that.
And it's nice. Seamless. It's nice for the user, and I don't have to
deal with refilling fields unnecessarily.
But the same trick doesn't work with ASP.NET, because it's server
based. Remote Scripting, in theory, should do much the same thing.
So here are my questions:
* Have any of you worked with Remote Scripting in your ASP.NET apps?
* Is it worth it? Is it a mess? If I decide to jump into the deep
end, am I going to regret it, or is this a practical solution?
Opinions for and against are welcome. I'm wholly ignorant on the
subject.