runat="both" to allow validation or other logic to be run in both places.
Some of the changes that we've made to DWR will only help you if you are using DWR inside Jaxer, but others could be generally useful.
There are 2 basic changes. DWR on the Internet needs to make sure that the Internet only touches the code that you want it to touch. DWR in Jaxer doesn't have this problem because it's not accessible from the Internet, so we can do away with almost all configuration. Secondly latency inside a server-room is tiny compared with the net, which makes synchronous XHR viable.
So as it stands at the moment in development, you can use DWR inside Jaxer like this (clearly this is subject to change):
There are a number of benefits that come out of this even if you're not using Jaxer:
- Cross domain remoting is now automatically detected, and scriptTag remoting is used if needed.
- There is a new init-param 'useAbsolutePaths' which might help people with trouble remapping DWR's location.
- All URLs are now reconfigurable.
- If you are using DWR in synchronous mode (which I don't recommend on the Internet) then you can use returned data in the normal way without needing a callback.