G
Guest
I'm trying to determine if we want to use panels or user controls for our
pages. Our primary concern is performance, page loading and posting speed.
To illustrate my question, lets use the Customer Orders scenario:
Problem:
User needs to view orders and and edit, add, save on one page called
Orders.aspx. To begin with the page contains a grid with basic information
about an order. The user can click a row to edit or click an "Add" button to
add a new order.
When the user clicks edit or add some controls appear below the grid
allowing them to input data, and then save.
User Control Proposal:
We have the Orders.aspx page and two user controls. The user control with
the grid is called ucOrders.ascx and the user control allowing user input is
called ucChangeOrders.ascx.
The two user controls are on the page during design time, therefore they are
not loaded on the fly during runtime.
When the user clicks the edit button on the ucOrders.ascx control it raises
an event that the Orders.aspx page listens for and then passes the order id
to the ucChangeOrders.ascx page that populates its child controls with the
current data the user can change. When the user clicks save on the
ucChangeOrders.ascx control it raises an event that the Orders.aspx page
listens for to know a save has been done and react to it appropriately.
From a design perspective this approach allows the user controls to be
self-contained with the parent page acting as the controler. It is easier to
follow, the page is not bulky and easier to maintain. However, we fear a
performance hit for doing this will not justify doing it this way when
compared to using panels.
Panels Proposal:
The panels approach is very similar to the User Control approach. The
difference being that the panels are on one page rather than being broken out
to separate files. Of course now you have to maintain panel visibility and
such for the panel that allows input below the grid.
Which is faster? And why? And is there any documentation to back up your
answer?
pages. Our primary concern is performance, page loading and posting speed.
To illustrate my question, lets use the Customer Orders scenario:
Problem:
User needs to view orders and and edit, add, save on one page called
Orders.aspx. To begin with the page contains a grid with basic information
about an order. The user can click a row to edit or click an "Add" button to
add a new order.
When the user clicks edit or add some controls appear below the grid
allowing them to input data, and then save.
User Control Proposal:
We have the Orders.aspx page and two user controls. The user control with
the grid is called ucOrders.ascx and the user control allowing user input is
called ucChangeOrders.ascx.
The two user controls are on the page during design time, therefore they are
not loaded on the fly during runtime.
When the user clicks the edit button on the ucOrders.ascx control it raises
an event that the Orders.aspx page listens for and then passes the order id
to the ucChangeOrders.ascx page that populates its child controls with the
current data the user can change. When the user clicks save on the
ucChangeOrders.ascx control it raises an event that the Orders.aspx page
listens for to know a save has been done and react to it appropriately.
From a design perspective this approach allows the user controls to be
self-contained with the parent page acting as the controler. It is easier to
follow, the page is not bulky and easier to maintain. However, we fear a
performance hit for doing this will not justify doing it this way when
compared to using panels.
Panels Proposal:
The panels approach is very similar to the User Control approach. The
difference being that the panels are on one page rather than being broken out
to separate files. Of course now you have to maintain panel visibility and
such for the panel that allows input below the grid.
Which is faster? And why? And is there any documentation to back up your
answer?