Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Persistence in WebParts
Message
General information
Forum:
ASP.NET
Category:
Class design
Environment versions
Environment:
C# 2.0
Database:
MS SQL Server
Miscellaneous
Thread ID:
01146511
Message ID:
01147274
Views:
19
Rick,

Thanks for the response. I have started looking at ATLAS. In my initial testing with it, I have two grids on the form, each in their own UpdatePanel. If I re-sort a column in one of the grids, the page is calling back to update both grids. The query for each grid is run against the database, but only the grid I clicked on gets visually changed. So, only a portion of the page is being re-rendered, but the logic and data access for the entire page is still happening. This isn't acceptable for a dashboard/portal type of application where there can be x number of web parts on a page, each running queries against various databases. If I even minimized one of those components, I can't have every other component on the page pulling data again. The page would die in a heartbeat.

Over the weekend I started taking a look at the Google Web Toolkit. This seems to give much more control over individual components on the page. Have you looked at ATLAS any. I'm sure I must be doing something wrong. I can't imagine that it has to work the way I'm experiencing it right now.

Thanks,
Chad

>ATLAS is another option in that you can update parts of a page without refreshing all of it. This makes it possible to leave the bulk of the data alone and only update portions of the page that are actually affected.
>
>+++ Rick ---
_________________________________
There are 2 types of people in the world:
    Those who need closure
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform