By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,526 Members | 2,189 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,526 IT Pros & Developers. It's quick & easy.

AJAX libraries

P: n/a
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?
Apr 9 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
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.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Thirsty Traveler" <nf*@nospam.com> wrote in message
news:uF*************@TK2MSFTNGP02.phx.gbl...
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?

Apr 10 '06 #2

P: n/a
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..
"Thirsty Traveler" <nf*@nospam.com> wrote in message
news:uF*************@TK2MSFTNGP02.phx.gbl...
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?

Apr 10 '06 #3

P: n/a
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.

"Steve C. Orr [MVP, MCSD]" wrote:
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.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Thirsty Traveler" <nf*@nospam.com> wrote in message
news:uF*************@TK2MSFTNGP02.phx.gbl...
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?


Apr 10 '06 #4

P: n/a
http://www.daniel-zeiss.de/AJAXComparison/Results.htm
This is the comparison.
Just wanted to point out that the 99% of traffic for Atlas are static
scripts that loaded only once for the client. All other traffic less or on
the same level as ANTHEM.NET or AJAX.NET. See the charts on the bottom of
the article.
Thanks.

"Thirsty Traveler" <nf*@nospam.com> wrote in message
news:uF*************@TK2MSFTNGP02.phx.gbl...
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?

Apr 10 '06 #5

P: n/a
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.


Well, it's old enough to come with a go-live license ;-)
--
Joerg Jooss
ne********@joergjooss.de
Apr 10 '06 #6

P: n/a
DWS
Well it looks like you broke the bench mark agreements on everything. Can't
you read or don't you care.

"Thirsty Traveler" wrote:
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?

Apr 11 '06 #7

P: n/a
Have a nice day.

"DWS" <DW*@discussions.microsoft.com> wrote in message
news:06**********************************@microsof t.com...
Well it looks like you broke the bench mark agreements on everything.
Can't
you read or don't you care.

"Thirsty Traveler" wrote:
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?

Apr 11 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.