Excuse me if I'm asking something that is obvious, but I'm a little curious of the DNN Client API related to Atlas. I just had a look at www.live.com and www.start.com where Atlas is rather extreamly exposed.

How much of Atlas features can we make use of as we make PA's in DNN. 3.2/4.0. I've seen your examples, and understand that you have provided quite alot to make AJAX functionality available in DNN, but what I'm not quite sure of is how close/far your Client API are in feature and syntax related to Atlas.

I heavily depends of ICommunicate today, are there any features in the Client API that triggers a refresh of several modules as dynamic roundtrips or is this restricted to a module/control in singular? I guess that the call back are able to go to the default.aspx and some logic there manages the DHTML communication. This should open an opportunity to continue using iCommunicate if I manage to adress several modules in the same roundtrip.

I'm guessing here, and likes to hear some feedback on atlas compatibillity and opportunities to make use of ICommunicate in a atlas/client API scenario.

Cheers,
/Rob