Ajax.NET or the Atlas Framework?

I found a lot of blogs and articles that are asking if we should use the Ajax.NET library or the Atlas Framework. My opinion is that it is not easy to compare these two AJAX ideas. Ajax.NET was only a idea to have a data access for JavaScript with nearly the same objects as method argument or results like we are using on the server-side. There are some other companies with nice WebControls that support AJAX functions. What we need is both of them, some WebControls (like auto-complete or livesearch, a grid that will get data while paging through,...) and the possibility to read data with a minimum of code and JavaScript knowledge. The Atlas Framework will be a complete framework where you will get additional controls.

16 Comments

  • Dessi said

    Comment found on the blog: "Microsoft should just bring this guy up and work with him to create and integrate AJAX.NET into the .NET Framework as he has already submitted the request to put it in, instead of competing with him and squashing him flat with their weight. "

    I also think that they should conact Schwartz for the idea and for all the feedback we already have send to him.

    Schwartz, you are the MVP for AJAX, where can I vote for you??? Thanks for the support you have done for me!!!!!

  • Olaf said

    Will the Ajax.NET library will be part of the Atlas Framework? Michael, are you working at Microsoft?? I did not find any info about you where you come from...

  • Michael Schwarz said

    @Dessi: Hi, I am already in contact with Microsoft Redmond (Web Platform Team). I think there is no MVP voting page, sorry.

    @Olaf: No, the Ajax.NET library will not be included with the Atlas Framework, but perhaps we can get a similar way to get data back from the web server without the postback. I am from Germany, Nuremberg.

  • Dan Barthel said

    More to the point, should AJAX.NET be expanded to implement the full JSON-RPC specification. This would add features such as call to call state persistance, constructors, etc. I think this would be a far more effective path for this project. One of the immediate benefits would be the ability to cache datasets for rapid and efficient page refresh.

  • Michael Schwarz said

    @Manu: Yesterday I have signed a NDA for the Atlas Framework. Now, I will get more details about the framework and have the chance to give feedback from my and your Ajax.NET experience. If you have a good idea or a must have feature for Atlas Framework please use my contact form or the feedback here. I will collect all these mails to see if it is interessting for the Atlas Framework.

  • Mark E. said

    The reasons I have for using the AJAX.NET over Atas...

    1) AJAX.NET is here and now Atlas will come when??
    2) Assuming AJAX.NET *does* get released as OpenSource and the license is acceptable (ie. LGPL, BSD, etc) then I would much prefer AJAX.NET. I can see the code, I can add new features, fix bugs, and get releases and updates much more frequently.
    3) Knowing MS, Atlas will be closed (no source) will only work on the newer 2.0 framework, will have long dead times between patches and/or new features, I won't be able to contribute/fix/affect direction of the project no matter how hard I try.

    I will always prefer an OpenSource and separate project over a built-in closed source one. Releases can be faster, more people can be involved and it will generally work on older/existing products.

    -Mark E.

  • Doris mILLER said

    Hello, I downloaded the AJAX library for some weeks ago and changed all my web apps, very cool thing. What will ATLAS be, a collection of controls and something like the AJAX.NET? Where can I get more info?

  • Manu said

    Schwarz, I hope that you can change Atlas team mind to make what you think it's better for the community because of your experience with AJAX.NET. I hope at least they pay you something ;-)

    Because of you NDA you can't tell us anything so...good luck man!

  • Mike said

    Hey, if Atlas is not as good as Ajax.NET there is nothing stopping folks from using Ajax.NET and continually extending/using it. I throw out MS parts of the Framework all the time. This is no different!

    Regards,
    -Mike

Comments have been disabled for this content.