In ASP.NET, is a rendered control required?
<p>Normally when creating a server control, you create a collection of controls that get added to the control collection and are then rendered into the HTML.  If you need to ensure that the properties of the server control (other than input information) is maintained bewteen postbacks, you use the control state to hold this information.</p>

<p>So, would it be possible to create a server control that has no child controls to be rendered, but does have control state information saved between postbacks?</p>
