DWR

Automatically allow YUI performance #6

We can't just do an <script src="dwr/everything.js"/> because that would give away the complete list of exported classes - something that we forbid for security reasons right now. Plus there are good reasons for only wanting the interfaces that you use on the existing page.

Bu how about:
<script src="dwr/getResources?include=utils,MyInterface1,MyInterface,..."/>

There are some issues, like what if someone has exported a class called utils, but the general idea is very close. Maybe we should force people to write interface/MyInterface1 or something similar. We actively want this to be cached - I wonder if there are any cases where parameters inhibit caching?

I wonder if it'd be more natural to have something like Dojo's djConfig structure? Define that before the <script> tag that loads DWR's client code, and there you can set what interfaces to load, any cache settings, whatever else might get added down the road... I'm just thinking in terms of being a developer, which is more natual? ...

<script src="app/dwr/include=interface/class1,interface/class2&noCache=true"></script>

...or...

<script>
 var dwrConfig = {
  include : [ "interface/class1", "interface/class2" ],
  noCache : true
};
</script>
<script src="app/dwr/dwr.js"></script>

Yes, it's more typing certainly, but I'm just thinking about some cases I have where I may have 10-15 or more classes being imported, do I really want to do that on one long line as a query string, or is it more natural to do it in Javascript like that? Also, I think it makes it so that you always load dwr.js and nothing else, so *maybe* it's simpler (I'm not so sure about that).