By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,771 Members | 1,709 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,771 IT Pros & Developers. It's quick & easy.

trick for server-side execution without reloading page?

P: n/a
PJ6
After resigning myself to really learn JavaScript, I finally made my own
grid control that populates itself and updates data . It's actually pretty
sweet. The only problem I have with it is that every edit posts back, and
when that happens, the browser accumulates a history of old page states that
are no longer valid. I read some about the "Redirect After Post pattern" but
can only find articles that explain it in terms of Struts. Maybe someone
could explain to me how it would work in ASP.NET?

I also had the idea that I could have the edit updating action open a new
window, have that POST to execute server-side code, and then close. No
history accumulation. Only that's kind of ugly considering many users have
popup blockers and having a window pop up, however briefly, for each edit
would probably be pretty annoying.

So what's the best way to approach this?

Thanks in advance to anyone who can help,
Paul
Dec 5 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
I'm not 100% sure but I think the new Grid Control in ASP.NET 2.0 does
that already. Otherwise try out Ajax, which is the hype of the moment
to do async callbacks without actual page reloads. Microsoft has an
Ajax implementation called Atlas, but if you google for Ajax and .NET
you should find tons of stuff.

Remy Blaettler
www.collaboral.com

Dec 5 '05 #2

P: n/a
Another option would be perhaps to prevent cahing ?
http://support.microsoft.com/kb/234067/en-us

--

"PJ6" <no****@nowhere.net> a écrit dans le message de
news:%2******************@TK2MSFTNGP14.phx.gbl...
After resigning myself to really learn JavaScript, I finally made my own
grid control that populates itself and updates data . It's actually pretty
sweet. The only problem I have with it is that every edit posts back, and
when that happens, the browser accumulates a history of old page states that are no longer valid. I read some about the "Redirect After Post pattern" but can only find articles that explain it in terms of Struts. Maybe someone
could explain to me how it would work in ASP.NET?

I also had the idea that I could have the edit updating action open a new
window, have that POST to execute server-side code, and then close. No
history accumulation. Only that's kind of ugly considering many users have
popup blockers and having a window pop up, however briefly, for each edit
would probably be pretty annoying.

So what's the best way to approach this?

Thanks in advance to anyone who can help,
Paul

Dec 5 '05 #3

P: n/a
PJ6
"Spam Catcher" <sp**********@rogers.com> wrote in message
news:Xn**********************************@127.0.0. 1...
Take a look at AJAX and Client Side Postbacks - these technologies will
allow you to postback data (and retrieve data) without reloading a
webpage.


Great suggestion! I got it working for a simple case but I'm having a
problem with response.value being always null in the project I care about...
I'll get it eventually I hope.

Thanks,
Paul
Dec 5 '05 #4

P: n/a
PJ6
w00t I got it my class was abstact and I had to make the server-side method
static.

:)

Paul

"PJ6" <no****@nowhere.net> wrote in message
news:%2******************@TK2MSFTNGP12.phx.gbl...
"Spam Catcher" <sp**********@rogers.com> wrote in message
news:Xn**********************************@127.0.0. 1...
Take a look at AJAX and Client Side Postbacks - these technologies will
allow you to postback data (and retrieve data) without reloading a
webpage.


Great suggestion! I got it working for a simple case but I'm having a
problem with response.value being always null in the project I care
about... I'll get it eventually I hope.

Thanks,
Paul

Dec 5 '05 #5

P: n/a
How does preventing caching eliminate a POST

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Patrice" <no****@nowhere.com> wrote in message
news:O1**************@TK2MSFTNGP10.phx.gbl...
Another option would be perhaps to prevent cahing ?
http://support.microsoft.com/kb/234067/en-us

--

"PJ6" <no****@nowhere.net> a écrit dans le message de
news:%2******************@TK2MSFTNGP14.phx.gbl...
After resigning myself to really learn JavaScript, I finally made my own
grid control that populates itself and updates data . It's actually pretty sweet. The only problem I have with it is that every edit posts back, and when that happens, the browser accumulates a history of old page states

that
are no longer valid. I read some about the "Redirect After Post pattern"

but
can only find articles that explain it in terms of Struts. Maybe someone
could explain to me how it would work in ASP.NET?

I also had the idea that I could have the edit updating action open a new window, have that POST to execute server-side code, and then close. No
history accumulation. Only that's kind of ugly considering many users have popup blockers and having a window pop up, however briefly, for each edit would probably be pretty annoying.

So what's the best way to approach this?

Thanks in advance to anyone who can help,
Paul


Dec 5 '05 #6

P: n/a
It won't but my understanding is that the real problem is :
the browser accumulates a history of old page states that are no longer valid.

He then came with not posting as a way to solve this but it's not clear if
he tried some other path before...

--
Patrice

"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> a écrit dans le message de
news:ug****************@TK2MSFTNGP09.phx.gbl...
How does preventing caching eliminate a POST

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Patrice" <no****@nowhere.com> wrote in message
news:O1**************@TK2MSFTNGP10.phx.gbl...
Another option would be perhaps to prevent cahing ?
http://support.microsoft.com/kb/234067/en-us

--

"PJ6" <no****@nowhere.net> a écrit dans le message de
news:%2******************@TK2MSFTNGP14.phx.gbl...
After resigning myself to really learn JavaScript, I finally made my own grid control that populates itself and updates data . It's actually pretty sweet. The only problem I have with it is that every edit posts back, and when that happens, the browser accumulates a history of old page states that
are no longer valid. I read some about the "Redirect After Post
pattern"
but
can only find articles that explain it in terms of Struts. Maybe

someone could explain to me how it would work in ASP.NET?

I also had the idea that I could have the edit updating action open a

new window, have that POST to execute server-side code, and then close. No
history accumulation. Only that's kind of ugly considering many users have popup blockers and having a window pop up, however briefly, for each edit would probably be pretty annoying.

So what's the best way to approach this?

Thanks in advance to anyone who can help,
Paul



Dec 5 '05 #7

P: n/a
ok

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Patrice" <no****@nowhere.com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl...
It won't but my understanding is that the real problem is :
the browser accumulates a history of old page states that are no longer valid.

He then came with not posting as a way to solve this but it's not clear if
he tried some other path before...

--
Patrice

"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> a écrit dans le message de
news:ug****************@TK2MSFTNGP09.phx.gbl...
How does preventing caching eliminate a POST

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Patrice" <no****@nowhere.com> wrote in message
news:O1**************@TK2MSFTNGP10.phx.gbl...
Another option would be perhaps to prevent cahing ?
http://support.microsoft.com/kb/234067/en-us

--

"PJ6" <no****@nowhere.net> a écrit dans le message de
news:%2******************@TK2MSFTNGP14.phx.gbl...
> After resigning myself to really learn JavaScript, I finally made my own > grid control that populates itself and updates data . It's actually

pretty
> sweet. The only problem I have with it is that every edit posts back, and
> when that happens, the browser accumulates a history of old page states that
> are no longer valid. I read some about the "Redirect After Post pattern" but
> can only find articles that explain it in terms of Struts. Maybe someone > could explain to me how it would work in ASP.NET?
>
> I also had the idea that I could have the edit updating action open
a new
> window, have that POST to execute server-side code, and then close.
No > history accumulation. Only that's kind of ugly considering many

users have
> popup blockers and having a window pop up, however briefly, for each

edit
> would probably be pretty annoying.
>
> So what's the best way to approach this?
>
> Thanks in advance to anyone who can help,
> Paul
>
>



Dec 6 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.