Atlas vs Callback!

Hi,

wanted to ask in what way these two differs? Atlas uses a PartialRender and Callback uses a PartialRender as well? It seems that Atlas uses Postback and not Callback which in the case I'm seeing the part updated in an UpdatePanel to flicker as usual, on the other hand Callback doesn't suffer from such thing.. which is the most efficient? I believe Atlas is more secure than the Callback process but am I missing something? please let me know if someone knows so as to know whats best to use

Thank you

hello.

well, they're different approaches of refreshing the UI without performing a postback. most of the time, they noth use the xmlhttprequest object to comunicate with the server side.

hi,

I don't think so, the UpdatePanel in Atlas always performs a PostBack... check out when debugging and it sets PostBack to True when you click a control in an UpdatePan! ... they "noth" use? they don't use the xmlhttprequest? where's AJAX then?

thanks

hello.

well, i think that there's a misunderstanding regarding the word postback. i'm using it to imply a total page refresh. when you use an updaptepanel and you set the enablepartialrendering property of the scriptmanager, you'll get a partial postback. when this happens, the atlas client platform uses a hmlhttprequest object that is responsible for communicating with the server side and getting the new html that will be put inside the panel. during this, the ispostback property is set to true, but you'll also see that the isinpartialrederingmode property is set to true.

i do believe that this similar to what happens during an asp.net callback (though, in this case, the iscallback property of the page is set to true).

btw, both of these options fo use the xmlhttprequest object to initiate communication with the server side.