Expand all only expands currently loaded nodes + 1 or 2 requests deeper (it is possible to return more than one level per request) when using async on large trees. On non-async based trees expand all expands the entire tree.

It is not possible to attach a demo due to depending on large amounts of commercial server-side code that is not under an open license, however if you want to see a real world example you are welcome to contact isaac@light.net.nz and a demo account will be setup for you on our web-accessible industrial maintenance system. We have trees with several thousands nodes to use as a demo and we can easily generate even larger trees if required (e.g. 100k nodes is not a problem).

If trees get too large I guess expand all becomes useless, but its still inconsistent with non-async behaviour, prehaps a configurable depth setting for how far expand all will go each time is worth considering.