Hi:
I've just moved from RadControls classic to RadControls for Ajax so I'm exploring the many examples, etc. I came across the demo on inserting and update grid on client-side. It's cool and all, but I'm not sure what use these features have.
I mean, most grid data are from database backend, so you can update and insert all you want on the client-side, but without travelling back to the server, the changes won't persist. In fact, couldn't this whole client-side update cause a LOT of confusion, especially among less web-savvy users. I mean, they click the update button, they see the changes on screen real fast, they're happy and go for coffee, they come back and the session is over. They re-log on and all the changes are gone. And they're all confused as to why.
So, I'm not sure under what circumstances should client update or insert be used. To be honest, I can think of any. Am I missing something?
I'd really appreciate some feedback/clarification on this!
Justin
I've just moved from RadControls classic to RadControls for Ajax so I'm exploring the many examples, etc. I came across the demo on inserting and update grid on client-side. It's cool and all, but I'm not sure what use these features have.
I mean, most grid data are from database backend, so you can update and insert all you want on the client-side, but without travelling back to the server, the changes won't persist. In fact, couldn't this whole client-side update cause a LOT of confusion, especially among less web-savvy users. I mean, they click the update button, they see the changes on screen real fast, they're happy and go for coffee, they come back and the session is over. They re-log on and all the changes are gone. And they're all confused as to why.
So, I'm not sure under what circumstances should client update or insert be used. To be honest, I can think of any. Am I missing something?
I'd really appreciate some feedback/clarification on this!
Justin