hi all,
i am developing a page with a treeview where people can add and delete nodes clientside. My idea was to do this with trackchanges and commitchanges at each action of the user, WITHOUT going to the server at that point.
So if an user adds 2 nodes, the server does not know this at the moment.
I will only go to the server when the user chooses for a SAVE, this happens with a button. But.... does the button have to callback the treeview from the server to the client as well? Cause if i do not do this, i will get an index out of bounds the second time i press the SAVE button. (or when i add nodes, nodes get added each time i have a postback to the server).
What i want is that i can do changes at the client, and commit them to the server at the time the user chooses to save the data. BUT! i do not need / want to have to callback the data from the server back to the client, cause i allready know 100% sure my client state is the same as on the server.
I think above has something to do with the client state? Without a callback of the treeview from server to client, this is not emptied, but it is applied to the server (at poostback) by the clientside call commitchanges?
Cheers and thx,
i am developing a page with a treeview where people can add and delete nodes clientside. My idea was to do this with trackchanges and commitchanges at each action of the user, WITHOUT going to the server at that point.
So if an user adds 2 nodes, the server does not know this at the moment.
I will only go to the server when the user chooses for a SAVE, this happens with a button. But.... does the button have to callback the treeview from the server to the client as well? Cause if i do not do this, i will get an index out of bounds the second time i press the SAVE button. (or when i add nodes, nodes get added each time i have a postback to the server).
What i want is that i can do changes at the client, and commit them to the server at the time the user chooses to save the data. BUT! i do not need / want to have to callback the data from the server back to the client, cause i allready know 100% sure my client state is the same as on the server.
I think above has something to do with the client state? Without a callback of the treeview from server to client, this is not emptied, but it is applied to the server (at poostback) by the clientside call commitchanges?
Cheers and thx,