client callback versus atlas?

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

Hi,

I develop aspnet applications (no webservices) often using gridviews with
sorting and dropdownlist ...
I was wondering whether i could use 'ajax' methods for speeding up my
applications (e.g. when sorting, the whole page is refreshed) .
Now i read about client callback and atlas and i have some questions about
that.

1) what's the best i can use (atlas or client callback)?
2) isn't it going too far for just speeding up e.g. in case of sorting in a
gridview?

Thanks for advice
Bob
 
ATLAS is big (in the sense that the assembly is large) and injects a lot of
script. Unfortunately, clientcallback implementation is not very robust. A
good middle ground might be one of the better open-source Remote Scripting
("AJAX" if you must) frameworks such as Anthem.Net or MagicAjax, both of
which can be found on SourceForge.net
Peter
 
Thanks

Peter Bromberg said:
ATLAS is big (in the sense that the assembly is large) and injects a lot
of
script. Unfortunately, clientcallback implementation is not very robust. A
good middle ground might be one of the better open-source Remote Scripting
("AJAX" if you must) frameworks such as Anthem.Net or MagicAjax, both of
which can be found on SourceForge.net
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
Click to expand...
 
Back
Top