Sorry...just a newbee question....what is the benefit of creating a server side ajax control (custom or otherwise) that implements the IScriptInterface? The one thing you can do is to set js object values using tags, such as -
<ctrl:ServerAjaxCtrl ID="Ctrl1" prop1="val1" prop2="val2" runat="server" /> 

But you can do this using just client side javascript as well from what I am seeing....so I can do -
$create(myControls.Ctrl1, {"prop1":"val1","prop2":"val2"}, null, null, $get("Div1"));

So why would I do the former versus the latter? Is it because it gives me more dynamic control if I use a server side control for this?

Thanks in advance,
Jake.

jacob_poly:

Is it because it gives me more dynamic control if I use a server side control for this?

Well .... what I meant by dynamic control was having a little more control at runtime as to whether to create that component or not via server side code versus client side javascript. But that was just a product of my speculation and can be ignored. So the original question still remains...what is the benefit of doing it one way versus the other. Especially what is is the advantage of doing it via the IScriptInterface versus using the javascript version to achieve the same result.

Thanks,
Jacob.