AJAX libraries

  • Thread starter Thirsty Traveler
  • Start date
T

Thirsty Traveler

Peter Bromberg has an interesting article eggheadcafe discussing AJAX
libraries. He prefers ANTHEM.NET over AJAX.NET because it doesn't break the
stateful page model. Our developers are currently using AJAX.NET after
extensive research because ATLAS is currently not ready for prime-time and
much more verbose than AJAX.NET.

I was looking at some "Hello World" status on various libraies and ATLAS
does, indeed, result in much more traffic.

The total traffic in bytes was:

ASP.NET 2.0 without AJAX -- 3,470
AJAX.NET Pro -- 15,536
ATLAS -- 181,850
ANTHEM.NET -- 15,618

It appears that ANTHEM is competitive with AJAX.NET and likewise has the
advantage of not breaking the stateful Page model.

I am wondering what others think about this? Should we continue with
AJAX.NET, switch to ANTHEM.NET... or wait for ATLAS?
 
S

Steve C. Orr [MVP, MCSD]

Atlas is planned to be part of the next version of Visual Studio.
Therefore, if you learn another AJAX framework, you're probably just going
to need to learn Atlas anyway when the next version of Visual Studio comes
out.
 
T

Trapulo

I've used AJAX.NET and then switched to ANTHEM.

My opinion, Anthem is a lot better as object model and asp.net integration.
It seems either stable and.. it works. With Ajax.net I had many problem on
production environment. And Anthem is open source.

Atlas I think is too young.

Your test is good, however I think it can be better a test with a "real
page". A page with a large html source, so we can see how using AJAX can
reduce network traffic. I hope that in this scenario ASP.NET without AJAX
requires more bytes that an AJAX solution for a round trip to server..
 
G

Guest

Thing is though, with anthem, you don't realy have to learn anything. Sure
there are a few more properties and stuff with the anthem controls, but they
are just ASP.net controls with a few extra properties and methods. You can
pretty much start using them straight away.
 
J

Joerg Jooss

Thus wrote Trapulo,
I've used AJAX.NET and then switched to ANTHEM.

My opinion, Anthem is a lot better as object model and asp.net
integration. It seems either stable and.. it works. With Ajax.net I
had many problem on production environment. And Anthem is open source.

Atlas I think is too young.
Click to expand...

Well, it's old enough to come with a go-live license ;-)
 
G

Guest

Well it looks like you broke the bench mark agreements on everything. Can't
you read or don't you care.
 
Top