Atlas Framework
Atlas is a .NET based framework that helps developers to build rich web based applications, specifically AJAX based web apps very quickly without compromising factors like cross-browser support compatibility and performance.
What it contains?
Client Side Script Library
It contains a client side script library which is actually the script framework. It contains the code for making AJAX calls, writing dynamic HTML on page, populate auto-complete forms, refresh a particular part of the page at regular intervals(like cricket scores) and a lot of other dynamic stuff you can think off.
Server Side Framework
This is kind of a module which you import in your .NET code and use some controls from this module to enable this dynamic functionalities. If you are aware of .NET it has controls which are readily available for you that you can use in your page, a .aspx page. Similarly the atlas components are controls.
Let’s take an example where I want to refresh a part of the webpage, when the user clicks a link. Then what I do actually on my .NET coding is that, I enclose the block of page which should be refreshed in a block and configure certain things to it. For this specific functionality I add a trigger to this update panel,i.e, when this updated panel should be updated(on what event). My requirement here is that it should be updated on clicking a link. So what I do is just add a line of code on server,
Please note that this is not the exact .NET syntax. I am just explaining the concept, the source indicates that source of the event is the link object, event specifies the name of the link event for which the trigger happens and for specifies the destination.
Partial Rendering
Now that you have defined all these you are done with developing a AJAX enabled page. When you view this page in your web browser and click the link only the update block gets refreshed and not the whole page. Atlas uses a concept called partial rendering which means that a part of the page only which needs to be refreshed is rendered. Meaning Script at the client side hits the same URI with a additional header value called delta = true which indicates the server that it should render only the partial content and returns the response which is further processed by the atlas script framework loaded on client.
Some Internal Stuff
What happens really to achieve all these? When you add code in the server like Updatepanel, trigger, etc at the server it in turn creates a set of XML tags and attaches the XML with the response. Along with this the framework JS atlas.js is included in the response to be loaded. This framework contains code that parses the XML attached with the response. It parses and gets information about the various dynamic functionalities like the updatepanel we discussed above, triggers associated with it. Based on the information it grabs the javascript objects hosted by the browser and binds them with specific functionalities. So there is a specific contract between the atlas.js and the code that generates the XML info that is attached at the server side.
Available Controls
Following are some of the controls that are readily available on Atlas that I have heard of,
- UpdatePanel – updates a block of page like weather information in response to a trigger
- AutoCompletionExtender – associated with a textbox. Autocompletes textboxes as you typein. At server it is associated with a datasource from which the data for autocompletion has to be fetched.
- Timer Control – refeshes particular information periodically like cricket scores
- DragOverlayExtender – enables a asp:panel to be dragged and dropped in the UI. Also supports remembering the last position
- Progress Indicator – displays the progress of a particular process that is initiated
Browser Support
Currently the browsers that are supported are
- Microsoft Internet Explorer
- Mozilla Firefox
- Apple Safari
WIP to support other browsers like Opera.
.asmx
Well apart from the partial rendering atlas also supports complete AJAX. That is instead of contacting the same URI and get a partial content, ping a different URI and get the required content, a web service. For example in case of AutoCompletionExpander we can use a .asmx command as resource. You configure the trigger to call this command. What it returns is a set of data that matches fetched from the datasource that you mentioned.
FYA
All the above stuff is what I heard from Mr.Nikhil Khotari, Microsoft Architect for Atlas. Also there might be some concepts that I have misunderstood from what I heard. So forgive me if I am wrong.
